Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Build with one .prg with the source
Message
De
04/02/2022 13:14:09
Dragan Nedeljkovich
Now officially retired
Zrenjanin, Serbia
 
 
À
04/02/2022 12:52:18
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01683436
Message ID:
01683451
Vues:
42
>>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.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform