Without hints like debug text, the best that can be done is the machine
language in some pretty form. Even the simplest of assemblers uses symbolics
so raw machine instructions are almost worthless. Optimizing compliers are
killers as they do things that obscure logic like moving constant operations
outside of loops, embedding constants in instruction streams. etc.
A decompliier almost by definition can't exist without some form of the
source. Modern compiler suites have a unique front end for each language
generating an intermediate text that drives a common optimizing code
generation back end.
Find a disassembler on the net and see for yourself an .exe is an .exe
regardless of the original language.
"Maxime B." <gi****@msn.com> wrote in message
news:63**************************@posting.google.c om...
I have to modifie an old Visual Basic 1.0 application and we can't
find the source code. Someone knows if a decompiler exists for VB1?