Well, aren''t you a genius?

War Worlds - A 3D Real-Time Strategy game in development.

If the functions were all small, and the library was compiled in debug mode, then it would be easy. What about a 3 page function compiled in release mode? That''s a fair challenge.

(But why would anyone use a hex editor to read plain text?)

hey, Anonymous Poster where did you get the MSVC dissassembler from?

MSVC comes with a built in disassembler. You just click on the disassembly window when debugging something.

Yeah, that is what a decompiler is. But you can''t get ''your'' source code back for several reasons. Partly because of lost identifier names as you said. Partly because all comments are stripped out. And partly because information is lost in the transition from high-level language to low level. If you compile something like this:

typedef long uint32;uint32 x; 

A decompiler will probably give you:

int x; 

Even worse when you start using the STL:

for (std::string::iterator si = myString.begin(); std::string::iterator si != myString.end(); ++si){ // do something } 

will probably come back as:

for (char* x = &s[0]; x != s[10]; ++x){ // do something } 

due to the way stuff gets optimised. (Note that the s[10] is also a simplification... that is likely to in fact be a few function calls or something to resolve that first.)

And any instantiations of templates would probably get returned as several different versions of the same sort of procedure.

Basically, a lot of the semantic info is gone forever.

This is partly why nobody''s managed to do a good decompiler yet... because it would have to fill in the blanks.

Ok, thanks you guys. Guess I have to rewrite my code...oh well thats life.