http://www.securitytracker.com/alerts/2004/Feb/1009067.html

ANd it seems that there's a lot of "shit" "crap" and "fuck" in the leaked source code

http://www.kuro5hin.org/story/2004/2/15/71552/7795

quote:

---

Curse words: there are a dozen or so "fucks" and "shits", and hundreds of "craps". Some dissatisfaction with the compiler is expressed in private\shell\shell32\util.cpp:
// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work
// around the fucking peice of shit compiler we pass the last param as an void *instead of a LPITEMIDLIST

---

quote:

---

Some insight into Microsoft's famous daily build process is given in private\windows\media\avi\verinfo.16\verinfo.h:
*       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
* !!!!!!!IF YOU CHANGE TABS TO SPACES, YOU WILL BE KILLED!!!!!!!
*       !!!!!!!!!!!!!!DOING SO FUCKS THE BUILD PROCESS!!!!!!!!!!!!!!!!
*       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*       !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

---

quote:

---

There are also various references to idiots and morons, some external, some within Microsoft. The file private\ntos\rtl\heap.c, which dates from 1989, tells us
// The specific idiot in this case is Office95, which likes
// to free a random pointer when you start Word95 from a desktop
// shortcut.
The file private\ntos\w32\ntuser\kernel\swp.c from 11-Jul-1991 points at
* for idiots like MS-Access 2.0 who SetWindowPos( SWP_BOZO
* and blow away themselves on the shell, then lets
* just ignore their plea to be removed from the tray

---

quote:

---

Quality
Despite the above, the quality of the code is generally excellent. Modules are small, and procedures generally fit on a single screen. The commenting is very detailed about intentions, but doesn't fall into "add one to i" redundancy.

There is some variety in the commenting style. Sometimes blocks use a // at every line, sometimes the /* */ style. In some modules functions have a history, some do not. Some functions describe their variables in a comment block, some don't. Microsoft appears not to have fallen into the trap of enforcing over-rigid standards or universal use of over-complicated automatic tools. They seem to trust their developers to comment well, and they do.

---

Wow, a real insight in to the lives of ms coders...

Just readed the article,

I think they are just normal ppl that have to say something a different way if they are irritated

That sucks that the comments are included in this leak... major invasion of privacy for the developers... I'm sure they don't want anyone reading their unprofessional swearing...

uh...

linux kernel fuck count

And linux is open-source... so everyone can see their swearing

It does look a bit unproffesional, though

quote:

---

when you put it all together and consider that in the present kernel source, 275 credited kernel authors wrote over 1,895,964 lines of code and documentation (6,856,723 words) and only managed to cuss 29 times -- it would seem that these developers show incredible self restraint when expressing frustration, are complete professionals, are sedated, or are just enjoying what they do!

---

just to throw caution to the wind... it is illegal to post any of the Microsoft Windows 2000 / NT code... i suggestion you delete this thread.  You can have a law suit.... check microsoft.com or this forum for that matter, for the post about posting / having the source code.

yeah, yeah, I know... but I didn't search the thing for fuck and shit and crap.. I only quoted it!

I don't have the source, and I didn't read it. If the mods ask, I will remove (parts of) the quotes from that site.

Plusfan only actually quoted the comments, not code, and the comments come out during compiling (i think).  I really doubt that Microsoft will have the time or the care to complain about that, seeing as this will be all over the internet by now... maybe if it was any sort of useful code it would be different.

the comments don't come out after compiling as far as I know...

You think Microsoft distributes compiled programs with the comments still included somehow? That wouldn't make much sense...

yeah, agreed

the comments are there, so when you read the source, you understand why something is done.. Without comments, bug fixing is very hard, I think (don't really now, though.. never wrote big programs..)

Hmm... I think there's some misunderstanding going on here...

Of course the comments in the source code will stay after compiling, the compiler shouldn't change the source. However, the comments will not be included in the compiled binary; the compiler removes them.

good explanation, 'DZ.

Look around at some websites I've seen some comments in the odd JS codes with stuff like that...anyway I don't think Microsoft would let the source code have anything like that in I mean how unofficial would that look in case of a leak...Not only would they be a scandal of the source code leak they'd be the scandal of Bill Gates and his loyal minions being a bunch of drunken loud mouth C++ programmers...

This is very normal, anubis_kree_

Linux kernel fuck count