Re: BDS2006 exe sizes

Ian wrote:
[...]
If the compiler produces a large executable from such a simple program as those, then they aren't efficient enough in my book.

Even if the compiler produces executables which are far smaller than the competition for real projects? Your benchmark is meaningless. If you want to work with no support for a "Hello World" .exe, then don't use the VCL or RTL. Code it all from scratch. If you want to get some work done, stop worrying about your .exe size.

Cheers,
Nicholas Sherlock
.

Relevant Pages

  • Re: What is the execution "debug.print" command after compile?
    ... Procedure calls may have side-effects unknown to the compiler, ... >> However if you compile an exe with absolutely nothing in twice, ... > Wrong conclusion based on the size argument...the VB executables are ...
    (microsoft.public.vb.general.discussion)
  • Re: Storing data in the application/exe file
    ... Now when you make exe you dont have to worry from ... secondary form you again let Delphi have its way, ... The global variable that Delphi puts in each form unit is essentially ... but between two different executables is much more involved. ...
    (alt.comp.lang.borland-delphi)
  • Re: TSR of go32-v2.exe or TSR for unstubbed COFF executable loader available?
    ... Compile an .exe. ... Or, IIRC, you could load the DJGPP DPMI hosts as a TSRs, but that'd ... Int 21h's exec functions to execute other file types, ... MultiBoot executables like loadlin, PE binaries like HXLdr32, COFF ...
    (comp.os.msdos.djgpp)
  • Re: If APL Is So Wonderful, How Come APL Programmers Arent Rich
    ... compiled to a single EXE: ... >> Will APEX allow me to take a set of APL2 functions and produce an .EXE ... Compiler runs under APL+Win today, ...
    (comp.lang.apl)
  • Re: Building EXE Twice Produces Different Files
    ... It think the status bar control pulls in the latest ... project type an Active EXE or Standard EXE under the properties? ... the C2 compiler, but it ends up in the finished executable. ...
    (microsoft.public.vb.general.discussion)