Re: de-compiler
Not really. There used to be a decompiler for R4GL around but it was not particularly accurate and you usually did better writing from scratch to replicate the behavior. Art S. Kagel Jason Coyne wrote: > > we have informix application and the people who wrote it have gone out of > business - taking all source code - can we de-compile or reverse engineer > the application we have on site ? > > Thanks
On Mon, 11 Sep 2000 16:37:26 -0400, "Art S. Kagel" <kagel@bloomberg.net> wrote: >Not really. There used to be a decompiler for R4GL around but it was not >particularly accurate and you usually did better writing from scratch to >replicate the behavior. Actually, it was quite accurate at the time it was written, but it may have strayed as features were added to 4GL, since there was no test suite for it. But it wouldn't be very *useful* for the requested purpose -- in the absence of source code, it just dumped opcodes. If source code was *available*, it would cross-reference the source statements to the generated opcodes, which was a handy tool. Mainly useful for debugging the pcode compiler or runner, not so much for debugging the 4GL program itself. \\-: -- Alan Denney yosemite at accesscom.com "My childhood was typical... when I was insolent, I was placed in a burlap bag and beaten with reeds. Pretty standard, really." -- Dr. Evil
just ma 2c, someone want to write one? Anyone want to supply the structure of a 4go file(s) brett > On Mon, 11 Sep 2000 16:37:26 -0400, "Art S. Kagel" <kagel@bloomberg.net> > wrote: > > >Not really. There used to be a decompiler for R4GL around but it was not > >particularly accurate and you usually did better writing from scratch to > >replicate the behavior. > > Actually, it was quite accurate at the time it was written, but it may have > strayed as features were added to 4GL, since there was no test suite > for it. > > But it wouldn't be very *useful* for the requested purpose -- in the absence > of source code, it just dumped opcodes. If source code was *available*, > it would cross-reference the source statements to the generated opcodes, > which was a handy tool. Mainly useful for debugging the pcode compiler > or runner, not so much for debugging the 4GL program itself. \\-: > > >