# Talk:Hexspeak

WikiProject Writing systems (Rated Start-class, Low-importance)
This article falls within the scope of WikiProject Writing systems, a WikiProject interested in improving the encyclopaedic coverage and content of articles relating to writing systems on Wikipedia. If you would like to help out, you are welcome to drop by the project page and/or leave a query at the project’s talk page.
Start  This article has been rated as Start-Class on the project's quality scale.
Low  This article has been rated as Low-importance on the project's importance scale.
WikiProject Computing (Rated Start-class, Low-importance)
This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start  This article has been rated as Start-Class on the project's quality scale.
Low  This article has been rated as Low-importance on the project's importance scale.

## 16/32 bits

Hexspeak is mostly either 16 or 32 bits when it is used for magic numbers. Note the use of some digits can sometimes be used as letters. "1" can mean "L" or "I", "0" could mean "o", "5" could mean "S", "7" sometimes means "T" and so on.

Examples: dead, beef, bad, feed, f00d, c0de, babe, c001, d00d, 1d107, ea7, caca0, cafe, 7ea, 15, 9e7, b19, e.tc..

I've yet to see a 'real' example of someone using 6 or 9 as G, 5 as S, and 7 as t, or 1 as i. It's certainly doable, except it just wasn't done at the time (7 only vaguely looks like T, at best). I'd classify 5 and 7 as leet. I've also heard the opinion that 1 as i isn't real leet either.

• I've used them as leet, and they've been used like that on the GameFAQs <a href="http://boards.gamefaqs.com/">message boards</a> quite frequently. So yes, they would qualify more as leet than hexspeak.

I also object to separating 0xDEADBEEF (and others) and removing decaf. Most hexspeak is 32 bits (hence 0xbaadfeed). And "note the use" makes little sense when the examples come after.

OTOH, there is #C0FFEE (a light greeny cyan), but I've never seen html colors used in this way either (other than by me), so I didn't include it. Elektron 12:23, 2004 May 5 (UTC)

• And nobody would want coffee that color anyway. Someone might have puked in it. --SheeEttin 01:51, 24 February 2006 (UTC)
• Not surprising. Most hexspeak is fairly large in the number range and thus yields almost white or primary colours. Coffee is dark brown. Shinobu 12:55, 15 June 2007 (UTC)
• "For example: 1517AB19B17Ch ('Is it a big bitchz0rz!!'). Note, however, that it is impossible to just spell 'bitch' as a single word, as numbers in this notation that begin with a letter have to start with a zero to distinguish them from variable names. 'Bitch' would then be '0B17Ch'." Why is this in the article? It can be removed. So then it would just read "In the Intel assembly language, hexadecimal numbers are denoted by a 'h' suffix." I don't think an example of what a hex number that ends in 'h' looks like is even necessary, and certainly not this example which looks like an attempt to sneak in some typical juvenile 1337 into an unrelated article, i.e. vandalism. - Gripdamage

## Uppercase

Note: for inter-article consistency, hex digits should be uppercase (see WP:MOSNUM). Quarl (talk) 2006-12-16 10:55Z

## Monospace and Combinations and Deliberately Placement of 0xdeadbeef

Off-topic: I once had a BSOD in Windows 2000 where it reported some kind of memory violation at 0xdeadbeef. I thought it was a coincidence, but now that I see this article, it may just be a weird developer. On-topic: Should hex be written in <tt>-tags? And why do we list examples when it's possible to make so many if you use the segments listed further up on the talkpage?--Ysangkok 21:29, 4 February 2007 (UTC)

It is possible that whatever program you used (a BSOD implies a device driver, or perhaps the OS itself?) filled non-initialized space with DEADBEEF. If, because of a bug, the program tried to use an uninitialized pointer, the program would report an access violation at DEADBEEF, because it did not point to allocated space. Shinobu 12:51, 15 June 2007 (UTC)

## Merge with magic number

Perhaps this article is better merged into Magic number (programming), since there's not much else here and the rest of the article could be summed up as "The hexadecimal digits 0-F, as well as h, are sometimes used to represent letters." Shinobu 13:18, 15 June 2007 (UTC)

## 0ff1CE

0ff1CE is used in guids for microsoft office.. citation - http://support.microsoft.com/kb/928218

Worth adding? -75.73.141.201 (talk) 19:02, 26 March 2009 (UTC)

## Nonsensical description for 0xD15EA5E\0

From the article:

0xD15EA5E\0 ("disease") opens a game disc partition on the Wii video game console. (\0 is used to mark the end of a string. Also of note, it was 0xDEADBEEF on the Nintendo GameCube.)

This doesn't make any sense. \0 inserts a null byte, but the description of the hex constant has it being treated like a nybble. If it's really 0xD15EA5E0 then there's no special significance to the trailing 0 (it's not used to terminate a string in that usage), and it also ruins the value of the constant as a single readable english word. If it is in fact a string, then "disease\0" would be 0x6469736561636500.

Can anybody shed any light on this issue? Where was this factoid taken from?

Kevin Ballard (talk) 19:24, 26 March 2009 (UTC)

I found a reference to it here, according to it, there's no \0 in the end, so I will remove it of from the article, but will not add any reference since I can't use this site as WP:RS.~ƒoאŁoɠicƙtalk 16:00, 13 November 2009 (UTC)

## Designing magic numbers

The ending sentence "[...] which generates an unaligned pointer exception on many processor architectures if the constant is interpreted as a pointer value." was previously marked as 'citation needed'. I've removed this, since this 1) is an obvious fact I feel requires no citation for the technically competent, and 2) will never have an understandable citation for the technically incompetent —Preceding unsigned comment added by 70.184.12.189 (talk) 19:25, 28 May 2009 (UTC)

## Sources

As a formality, I've added {{cn}} tags to all the unsourced items in the list. I suspect most of them will be easy to find refs for, and I'm going to attempt it myself. However, this will be a useful way of discarding any of those that are suspect. Oli Filth(talk|contribs) 18:56, 28 June 2009 (UTC)

Thanks. They've needed cn tags for a long time. tedder (talk) 19:04, 28 June 2009 (UTC)

The multiboot header magic ("1BADB002") is explained as "I bad boot", but there's no reference for it, so I added a fact tag. I'm used to reading it "one bad booze", as "2" for "t" is not common (but in leetspeak used for Z). Feel free to add a citation if you have one. Jalwikip (talk) 07:16, 10 September 2010 (UTC)

## D0 CF 11 E0

D0 CF 11 E0 or "Docfile", the header of all Microsoft Office document files before 2003 (with Office 2003 and later, all office files are now PKZip). — Preceding unsigned comment added by 64.122.75.82 (talk) 09:24, 19 April 2012 (UTC)

In german 0xBADEAFFE is in use, which means "bathing (BADE) monkey (AFFE)", see w:de:Hexspeak. Maybe it's worth being added to the article. --Mosmas (talk) 13:43, 31 July 2014 (UTC)