Josh seems to be taking his time, so I'll post my best guess.
I immediately recognized it as disassembled x84 assembly, which I have little to no experience with
I first tried using a table to lookup each instruction's assembly representations, but after translating the first one, got really impatient and just ran it through a disassembler
55 89 e5
b8 39 05 00 00 5d c3
Which I'm pretty sure are basic instructions at the beginning and end of every function to push memory onto the stack to make room for the function, and then de-allocate that space and return once the function is done.
So that's just his super nerdy way of saying "begin post" and "end post".
Nice one, tried the same and gave up.
Looking at the code it actually sets up a standard stack frame for the function's local variables, then at the end loads 0x539 into eax, which represents the return value of the function.
Now, 0x539 is 1337 decimal.
PS: really psyched for Josh's next post on what happened last week. I really like the new techie posts, been hacking around with LEXX/BISON and YACC in the old days to implement a script language.
Josh, if you are going for performance, that is the way to go, you can generate really fast, low-down c parser code from a nice grammar file. Leastways that's what was the way to go about 20 years ago
, no idea what hot and cooking today.
Fly safe, commanders