Re: Source of EXE Size OT

Ralph wrote:
>
....
> If you all don't mind I would like to piggy-back on this thread and ask a
> question.
>
> There is a phenomena in VB6 when compiling to native code the exe will grow
> by a small amount with each compile, even if there has been NO change in
> code. The solution is generally to close the project, cleanout the files and
> go again. So there is no long lasting harm.
>
> But I have been curious all these years - has anyone ever come up with an
> explanation of where those extra bytes are coming from. I have occasionally
> googled, but never found anything but the complaints, never an answer. Doing
> a compare on the exe appears to show a growth in both .text and .data (tho
> seldom equal).

Can't say I ever noticed it (I don't look at .exe size too often--it's
whatever it's going to be, for the most part w/ a language like VB).

The only thing I can say wrt the question you pose is a recollection of
a discussion some time ago wherein it (iirc) appears the actual .exe
size is a multiple of 64k rather than the actual generated code size. I
do recall doing really quick 'n dirty check and added only a small bit
of code to a minimal project and discovered that it did appear to be
true at least in that instance.

I had forgotten this tidbit when responding to Dan. If it is true in
general, then one would expect that the code size would jump in
increments. I guess another question I didn't ask was whether he is
generating p-code or native and whether he has changed any of the
default compiler options (empahsize speed over size comes to mind).
.

Relevant Pages

  • Re: Printing variables to screen, when in debug
    ... >>> evaluation tool (CosmoScope). ... >>Are you aware of the immediate window, and the Debug object? ... > But do remove before compiling as they slow your program down. ... For example, Debug.Print statements, while ignored in the run-time .exe, are ...
    (microsoft.public.vb.general.discussion)
  • Re: Source of EXE Size OT
    ... Aside from any resources you may have added, the EXE will ... After compiling to native code for many years, ... >> default compiler options. ...
    (microsoft.public.vb.general.discussion)
  • Re: Update #1 - Initialization Failure on Running Apps...
    ... I have exactly the same problem after actually compiling the application. ... so when using the "old" exe and debug info things are ... then repair again and I'm hoping that it'll download a fresh update. ...
    (borland.public.delphi.non-technical)
  • Re: LNK1106: Invalid file or disk full: cannot seek to 0x68e2.
    ... > server and the users run the EXE from a shorcut on their desktop. ... The error you're getting - if it's network related - occurs when you save ... If that's not the case and you're already compiling locally, ...
    (microsoft.public.vb.general.discussion)
  • Re: you do not have access to make the required system configuration modifications
    ... First one that comes to mind is the space in the path. ... E.g. my server name ... > The windows folder rights/permissions allow full control, ...
    (microsoft.public.windowsxp.security_admin)