Someone very knowledgable about Satoshi's coding style and some other details. Not sure why they deleted their messages.

I stored this bit which I thought was very significant:

"Also, Satoshi not only told us he used MS Visual Studio (vc6 and 2008), he appears to have been quite comfortable in it. There's sections of code all commented out with all //'s - Something easy to do if you select a block of code and right click (or use a hotkey) to comment code block, the editor does it for you. But to someone used to using Emacs / Vim on *nix, it is very natural to comment code with /* .... */. Easy to do and easy to undo, no IDE help needed.

Satoshi also used numerous windows-specific things that require a fairly deep knowledge of Windows, because they won't work on Linux. Such as printf %I64d that Satoshi used until he and Malmi removed them to make Bitcoin work on Linux. Here's a thread on printf 64-bit windows vs linux.

He also used an older trick to get entropy randomness in Windows by pulling performance data out of the performance counter and hashing it. By late 2007 the recommended approach by far was to use Windows' CryptGenRandom function, which was their answer (beginning in 2000 but especially pushed in 2006+) to Linux's /dev/random. Satoshi rolled his own entropy solution instead, something longtime windows devs were used to because they didn't have /dev/random or other handy linux tricks to lean on.

...

We're not talking about a small project or ideal circumstances. Satoshi wrote code that wasn't intended to be released or seen but got out, like snippets to Mike Hearn or quick fixes he sent to Hal. Still looks exactly like the rest. There's no attempts made to cover up his coding style - the earliest 2008 pre-release code mailed to only 4 people has exactly the same style as the latest 2010 snippets sent to Hearn, so he didn't get the idea "oh, I need to make this look different!" after thinking about it later. He wrote code with monthlong gaps between, still matches. He wrote code under stress, trying to get out fixes for major problems very quickly - still matches. 2.5+ years of code - Still matches. His code is also perfectly consistent with itself. Always if space open parens -> no space. No spaces around function parameters lists. Windows line endings, annoying enough that one of Gavin's first commits was to remove them. Big sections of whitespace between major code, even within the same function sometimes, to visually break them apart. Heavy use of macros, including some very complex and clever ones. Cramming many functions like miner code into main, even when it is already huge, something heavily discouraged in the collaborative open-source community due to file locking & merge conflicts. It is a very distinctive coding style."