[Coco] Re: creatdsk.c source

Robert Gault robert.gault at worldnet.att.net
Sat Dec 24 14:42:51 EST 2005

Even so, cc or cc1 will probably require more memory, as was reported. I 
see exactly the same thing when compiling ml code with asm. When you 
have ifp1 use /dd/defs/defsfile, you must assign about #30K extra memory 
or there is an error. The compiled code does not change size but in 
effect the size of the source has increased significantly.

tim lindner wrote:

> Mannequin* <mannslists at invigorated.org> wrote:
>>In Microware C, you didn't have to include string.h when you used the
>>string manipulation functions? Wouldn't that have added to the
>>executables size with those (and other) functions compiled in and not
>>being used?
>>Anyone want to explain this for me?
> Header files don't add to the executable size becuse they (usually)
> don't include any executable code. They usually only include
> declarations. Sometime they can include static data, but it is usually
> tiny. string.h doesn't contain any static data.
> Only calling functions defined in a header file will cause the linker to
> add the code that implements the function.

More information about the Coco mailing list