source code leaked; bug found |
Author: |
Message: |
user2319
Disabled Account
Posts: 1779
Joined: Oct 2002
Status: Away
|
O.P. source code leaked; bug found
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.
|
|
02-16-2004 07:56 PM |
|
|
fluffy_lobster
Veteran Member
Posts: -2
Posts: 1391 Reputation: 23
36 / /
Joined: Nov 2002
|
RE: source code leaked; bug found
Wow, a real insight in to the lives of ms coders...
|
|
02-16-2004 08:07 PM |
|
|
Huuf
Full Member
Posts: 482
44 / / –
Joined: May 2003
|
RE: source code leaked; bug found
Just readed the article,
I think they are just normal ppl that have to say something a different way if they are irritated
|
|
02-16-2004 08:25 PM |
|
|
WDZ
Former Admin
Posts: 7106 Reputation: 107
– / /
Joined: Mar 2002
|
RE: source code leaked; bug found
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...
|
|
02-16-2004 08:31 PM |
|
|
user2319
Disabled Account
Posts: 1779
Joined: Oct 2002
Status: Away
|
O.P. RE: source code leaked; bug found
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!
This post was edited on 02-16-2004 at 08:44 PM by user2319.
|
|
02-16-2004 08:41 PM |
|
|
lylesback2
Veteran Member
[lylesback2]
Posts: 1786 Reputation: 1
39 / / –
Joined: Jan 2003
Status: Away
|
RE: source code leaked; bug found
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.
<skanky>lylesback2</lanky>
3 days, 4 hours, 2 minutes, 56 seconds till the end of the world
|
|
02-16-2004 09:44 PM |
|
|
user2319
Disabled Account
Posts: 1779
Joined: Oct 2002
Status: Away
|
O.P. RE: source code leaked; bug found
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.
|
|
02-17-2004 06:57 AM |
|
|
fluffy_lobster
Veteran Member
Posts: -2
Posts: 1391 Reputation: 23
36 / /
Joined: Nov 2002
|
RE: source code leaked; bug found
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.
|
|
02-17-2004 02:30 PM |
|
|
user2319
Disabled Account
Posts: 1779
Joined: Oct 2002
Status: Away
|
O.P. RE: source code leaked; bug found
the comments don't come out after compiling as far as I know...
|
|
02-17-2004 02:36 PM |
|
|
WDZ
Former Admin
Posts: 7106 Reputation: 107
– / /
Joined: Mar 2002
|
RE: source code leaked; bug found
You think Microsoft distributes compiled programs with the comments still included somehow? That wouldn't make much sense...
|
|
02-17-2004 02:54 PM |
|
|
Pages: (2):
« First
[ 1 ]
2
»
Last »
|
|