>>>>>And how much larger is the other one?
>>>>
>>>>The size difference does depend on the contents of the APP/EXE file. From what I'd seen, enabling debug information generally doesn't affect report and label forms (since they usually don't contain program code),
>>>
>>>But they might... though they are just as bad a place where to insert code as the DE of a form. The last place where anyone would look. Also hard to spot in the debugger. So people generally avoid those places.
>>>
>>>>but PRG and screen forms are affected. I've seen EXE/APP balloon to twice the size when debug information is enabled (if I'm not mistaken, an EXE generated from VFP is essentially an APP, which consists of the p-code, bundled with vfpXrun.exe - where X corresponds to the version of VFP used).
>>>
>>>Yup, so it is.
>>>
>>>The size difference isn't necessarily that much - for .prg files, IIRC, only the .fxp is stored anyway (and it has what it needs for both cases, perhaps without comments if no debug info), it's the vcx/scx code that gets included differently. And also there are other files which influence the size - various bitmaps, included tables etc, which may be carried inside the exe for very good reasons. Their size doesn't change with the debug option.
>>
>>Let's say the size difference depends very much on the comments. FXP and the like come without, but a prg could quadrupple it's size just by comments w/o any problem.
>
>One thing that I'm not sure about is how the additional debug code is encoded in the file -- i.e. is the debug information stored "in-line" within the p-code (essentially acting like a comment like in a tokanized form of interpretive BASIC program), or is it stored in a different section that is essentially a lookup table that translates between offset within p-code file and the corresponding line number in the source. If it is the former, then the process of stripping out the debug information could get involved (since you'd probably have to perform "fixup" of any offset within the p-code file), while with the latter it might be easier (i.e. remove the debug part and modify the flags that indicate its presence).
>
>It also goes without saying that not selecting the encrypt option will generally result in a p-code FXP/APP file that can be more readily compressed (i.e. will be smaller when compressed).

I guess I'm wrong and it is the later version, kind of lookup. One need the external file to debug. Encrypt option? There is a switch somewhere, but since the program decrypting is cheap it had never any use. :)

Have a nice weekend.