Disclaimer:
Our very generous guarantee assumes that the following rules
are obeyed:
| |
1)
The program to be decompiled was originally compiled
without any errors. |
| |
2)
The program to be decompiled is identical to the
originally compiled program and it has not been
mangled by transmission errors, hard-drive corruption,
faulty network cards, viruses, or any programs. |
| |
3)
When the program is decompiled, the FILELIST.CFG
must be functionally identical to the FILELIST.CFG
that was used to compile the original program.
This means that datafiles can be added to the FILELIST.CFG
and unused datafiles can be removed. Datafiles
that are used by the .FLX program must have the
same filelist number both before original compilation
and while the .FLX is being decompiled. |
| |
4)
The .FD files supplied when the program is recompiled
must be functionally identical to the .FD files
that were used to compile the original program.
This means that field definitions much be identical
between the original .FD and the current .FD.
New fields can be added to the end of a datafile
definition without affecting decompiling. |
| |
5)
When the program is recompiled, an unmodified FLEX.CFL
(as provided by Data
Access Corporation) is used. |
Notes:
The .TAG
files used for decompiling do not have to be identical
to the original .TAG files that were used to compile
the program. They must, however, match the .FD file(s)
that are used for recompiling. The name of a field
is only a cosmetic issue. Calling a field Customer.Address
or Customer.Addr or Customer.Field_3 does not affect
the decompiler as long as the .FD file calls the same
field Customer.Address, Customer.Addr or Customer.Field_3.
The DataFlex
Decompilers target the source code for the same version
of DataFlex as the .FLX file. Recompiling a source
file under a different version of DataFlex may require
programmer induced changes, just like the original sources
would have had to be modified.
The DataFlex
decompilers can usually generate some kind of code even
when some of the rules are not valid. The generated
code may use generic filenames or field names.
In the case of #5, the FLEX.CFL can contain new custom
macros that were not provided by Data
Access Corporation without affecting how the recompiled
program behaves.
If you have
specific questions about the quality of a program's
code when you can't follow all of the rules in
the disclaimer, then please see
our Decompiler FAQ or contact us by emailing
to get an answer. More Information:
|
