Rethinking How BIG should MY.EXE become? 4

[pt777]

I've condensed 'MY.EXE' down to 3 Mbytes and 550 symbols (VFP9). I've packed/cleaned classes and do use a single 'LIBS' folder (vs. the VFP\FFC folder).

Likewise, Included Bitmaps and Reports are not very large.

Is the App too big? I'm paranoid about bloating up redundant classes from the FFC folder(s), because they cause MY.EXE to become larger and larger.

I realize that FFC's might be 'chomosomal-like' in that they may be regarded as a coding foundation for perhaps every 'cell-like-app' (if you will).

Any general suggestions by anyone? Thanks in advance.

 

[Mike Gagnon]

Have you removed the debug info before re-compiling?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[pt777]

Mike, I have not so much as heard of 'the debug info', I'll look at that now.

Thanks,
Philip

 

[Germancho]

Select Project --> Project Info --> Debug Info.

Be sure the Checkbox is not selected.

Best regards,

Germán Restrepo
Bogotá, Colombia

 

[Nro]

Hell, Germancho, I did not know this trick. One of my EXE file pass from 12mb to 7mb, only by uncheking Debug Info.

Thanks

Nro

 

[pt777]

...And mine dropped from 3MB to 2.3MB (just now).

But Nro's condensed 7MB file still seems a bit large. I'm still curious how large can an EXE get before expecting complications?

 

[Nro]

The only problem I have with such big file is that I have to run it from the client station instead of the server. But for anything else, I have one project that has a 10Mb .exe and it work fine.

Nro

 

[Olaf Doschke]

There should be no problem even if the exe grows much larger. As a foxpor exe is just a runtime loader module with an 'archive' of all the projects components like vcx,scx,frx,prgs etc., it hasn't really got a limit, even not the 2GB limit of DBF files etc.

There is a limit, that a single procedure/method etc. can't be larger than 65 KB of compiled code, but I wonder who would ever need that much for a single method.

If you don't include DEBUG info you can't log the code of the line causing the error: Message(1). But you may live with that.

Bye, Olaf.

 

[pt777]

OK then. I feel more confident now about redundancy-coding with the ffc's themselves. Thanks all.

In sum, if many ffc's were used in compiling big apps, I shouldn't much regard that old 'lean-and-clean' programming paradigm.

Philip