Microsoft geek humor
-
While going through a list of file errors that I need to handle, came across this one: ERROR_ARENA_TRASHED
//
// MessageId: ERROR_ARENA_TRASHED
//
// MessageText:
//
// The storage control blocks were destroyed.
//
#define ERROR_ARENA_TRASHED 7LWas somebody smoking weed when naming this error? :)
-
While going through a list of file errors that I need to handle, came across this one: ERROR_ARENA_TRASHED
//
// MessageId: ERROR_ARENA_TRASHED
//
// MessageText:
//
// The storage control blocks were destroyed.
//
#define ERROR_ARENA_TRASHED 7LWas somebody smoking weed when naming this error? :)
Damir Valiulin wrote:
Was somebody smoking weed when naming this error?
I thought you weren't supposed to name errors unless you were stoned....programming too. Damn it to hell, I have been doing wrong all these years.
-
While going through a list of file errors that I need to handle, came across this one: ERROR_ARENA_TRASHED
//
// MessageId: ERROR_ARENA_TRASHED
//
// MessageText:
//
// The storage control blocks were destroyed.
//
#define ERROR_ARENA_TRASHED 7LWas somebody smoking weed when naming this error? :)
Dude I didn't think anyone would ever see it. :cool:
Even a blind squirrel gets a nut occasionally. http://www.hq4thmarinescomm.com[^] [My Site]
-
While going through a list of file errors that I need to handle, came across this one: ERROR_ARENA_TRASHED
//
// MessageId: ERROR_ARENA_TRASHED
//
// MessageText:
//
// The storage control blocks were destroyed.
//
#define ERROR_ARENA_TRASHED 7LWas somebody smoking weed when naming this error? :)
Arena is a common name for the area where allocations take place (think of applications battling for memory ;)), and thrashing memory is a common expression. So I'd say the geek in question was verify serious about barbarian coders thrashing his beatifully managed arena.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
While going through a list of file errors that I need to handle, came across this one: ERROR_ARENA_TRASHED
//
// MessageId: ERROR_ARENA_TRASHED
//
// MessageText:
//
// The storage control blocks were destroyed.
//
#define ERROR_ARENA_TRASHED 7LWas somebody smoking weed when naming this error? :)
speaking of codes, I was going thru a program for an embedded processor programming replicator and found these codes: Code to program the write lock key (blows the security fuse): 0xDEAD, 0xBABE and in the Flash Write section (JTAG mailbox read status): 0xABADBABE and 0xCAFEBABE :cool: , :thumbsup: and :laugh:
Steve _________________ I C(++) therefore I am
-
Arena is a common name for the area where allocations take place (think of applications battling for memory ;)), and thrashing memory is a common expression. So I'd say the geek in question was verify serious about barbarian coders thrashing his beatifully managed arena.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchypeterchen wrote:
thrashing memory is a common expression. So I'd say the geek in question was verify serious
Yes, but thrashing memory (doing nothing productive while doing a lot of work) and trashing memory (doing a lot while doing no productive work) are two different things.
#define ERROR_ARENA_TRASHED
Have you verified that the geek was very serious?:confused:
Gary
-
speaking of codes, I was going thru a program for an embedded processor programming replicator and found these codes: Code to program the write lock key (blows the security fuse): 0xDEAD, 0xBABE and in the Flash Write section (JTAG mailbox read status): 0xABADBABE and 0xCAFEBABE :cool: , :thumbsup: and :laugh:
Steve _________________ I C(++) therefore I am
-
speaking of codes, I was going thru a program for an embedded processor programming replicator and found these codes: Code to program the write lock key (blows the security fuse): 0xDEAD, 0xBABE and in the Flash Write section (JTAG mailbox read status): 0xABADBABE and 0xCAFEBABE :cool: , :thumbsup: and :laugh:
Steve _________________ I C(++) therefore I am
Look at the first 4 bytes of any Java .class file. There's your CAFEBABE. A couple of months ago someone posted here a link to a discussion of what words you could "spell" in hex, some including various extra mappings (like 7 -> T) Cheers, Peter
Software rusts. Simon Stephenson, ca 1994.
-
speaking of codes, I was going thru a program for an embedded processor programming replicator and found these codes: Code to program the write lock key (blows the security fuse): 0xDEAD, 0xBABE and in the Flash Write section (JTAG mailbox read status): 0xABADBABE and 0xCAFEBABE :cool: , :thumbsup: and :laugh:
Steve _________________ I C(++) therefore I am
Those magical hex numbers already were popular 30 years ago. How about 0xDEADC0DE?
"I have what could be described as the most wide-open sense of humor on the site, and if I don't think something is funny, then it really isn't." - JSOC, 2011 -----
"Friar Modest never was a prior" - Italian proverb
