Thread by @bigendiansmalls, thread of grep'ing the XP source for interesting bits... "hack" ... don't [...]

thread of grep'ing the XP source for interesting bits...

"hack" ... don't do this, there are thousands.
but some funny ones:
"It probably is a file created by a hacker."
"a hacker can introduce a file in the datastore"
" This is a temporary hack [..] to keep out the casual observer/hacker. It should be replaced"

"ugly hackery required to extract directly into an enum"
"MIDL chokes on this, however, so we have this ugly hackery instead. Ugh."
(ugh lol)
"address, which can allow a hacker to hijack a program's execution."

"this file can be used by hackers for offline attacks."

Grep "crap"
"so they won't have a bunch of extra crap in them"
"write out the header crap"
"lists would be fairly simple, just more crap to add"
"then skip all this crap"
"only works if the server doesn't send extra crap"
"old crap still works"

Grep "terrible"
"it is not death, but dying, which is terrible."
"a terrible implementation"
"a terrible kludge"
"then something terrible happened"
"Did something terrible happen?"
"performance will be terrible"

grep -Rw "todo". (lololol)
" //todo, else, should bitch"
"//todo, bitch"
"todo, more error checking in here???"
" //todo, is 1 ok??"
"todo: get ride off this hack. See bug # 389483"
(there were so many of these I just gave up)

BUGBUG / CODEWORK / REVIEW
"BUGBUG: does this do anything"
"what does this do upon failure? what will it display?"
" what does this do?"
"REVIEW, what does this do for NULL?"
(there are 1000's of these searches)

!!!!!!!!!!!!!!!!!!!!!!!

"BUGBUG: HACK: WE SHOULD NOT BE PASSING A POINTER THROUGH AN AUTOMATION INTERFACE!!"

grep -iRw "this is bad"
" errors. This is bad-- needs to be changed."
"// This is bad!"
"// um, this is bad."

" // wow this is bad too!"
"// THIS IS BAD."
"// THIS IS BAD BAD BAD -- fix later BUGBUG"

// this is bad because it monopolizes the cpu, but since we're spinlocked anyway, what the heck, do it.

grep "what the heck"
"but what the heck, I'm lazy (or stoopid)"
"not necessary to set this, but what the heck"
"and, oh what the heck - let's copy the keys, too..."
"a little sleazy but what the heck"
"What the heck does a flag mask of 0 mean?"

"does anybody know what the hell this is"

"This shouldn't be needed (or shouldn't work)"

grep "hate"
"I really hate to create this static, but how else can I"
"If you hate the wrapping like *foolish tnoonan"
"I hate to have to do this..."
"We'd absolutely hate for this to happen on a read only volume"
" I really hate the GOTO, but in order to clean up, this is much"

"i hate async notification"
"I hate conditional assembly"
"I hate this, what if VPM sneaks in"
" I hate includes.exe"
"on the DOS version (don't you hate compatibility?)"
"We hate to use 0xff all the time as a test value, but"
"i hate includes of includes"

LOLOL +100
"I hate this cast but c'est la vie"

"more customer friendly but I hate to prevent future developers"
"This is weird, but i hate checking cArgs all over the place"
"we hate "new", but this is fine"

"don't call DsUnBind on an instance of this class: you'll only regret it later."

"this is spaghetti code at it's worst."

"doublecheck, I'm scared of the spaghetti..."
"spaghetti code at it's finest. Basically"

grep magical
"PERFORM CLEANUP OPERATIONS THAT ARE NORMALLY DONE AUTOMAGICALLY!"
"and if so, magically transforms"
"performs casts automagically"
"do magical stuff to hide everything"
!! "Note that this does not magically make single-thread code safe" !!

"Therefore, we can't just magically make this work."

"Don't change this code unless you GUARANTEE that whenever"
"don't change this comment!"
"so don't change this entry..."
"DON'T CHANGE THIS ALGORITHM NO MATTER HOW GOOD OF AN IDEA IT SEEMS TO BE!"

Just have to have so much respect for people who build this complex software. I think this sums it up:

grep "this is a mess"

Grep "who cares"
This doesn't cover the case of null strings, but who cares?
(Won't work with aggressive memory access reordering, but who cares <grin>)
/* NULL COUNT still only approximated. Who cares? */
any better than this at this point. who cares it makes director happy.

HACK - Win9x might go nuts as we can't check error return (who cares?)
Expensive, but who cares?
Who cares the user can't do anything about it anyway?!!! WHO CARES if it fails? They might not have audio h/w!TEMPORARY FIX WHO CARES WHAT HE WANTS? GIVE HIM WHAT OUR INPUTS

who cares, just return. It is the callers responsibility

Who cares about context sensitive help?

Call this last to clean up (or just let it fall off the end - who cares?)