🚀 go-pugleaf

In article <26252@cs.yale.edu> spolsky-joel@cs.yale.edu (Joel Spolsky) writes:
>In article <139400009@uxa.cso.uiuc.edu> klg0582@uxa.cso.uiuc.edu writes:
>>One thing I don't like for Turbo C is that the
>>executable code for the program of same purpose is larger in C than in
>>pascal. Is this generally true or is there a way to avoid this?

Even with all of the debug options turned off, Turbo C produces rather
bloated *.exe files.  The MKS Toolkit includes an analog to **IX strip
that will generally reduce *.exe files by 25-40%.

Essentially this does what one of the options in the MSC linker does,
if I remember correctly.  Assuming (I don't have time to check) the
processing is similar to **IX, tlink is probably leaving the symbol
table attached to the executable, although this has no subsequent use
(except with standalone debuggers).

One should also check for floating point library inclusion.  A single
floating point calculation, especially with emulation, will add
substantial overhead.  Moreover, simple floating point calculations can
often be replaced by integer operations.