[DUG] Delphi linker and library units

Kyley Harris KyleyHarris at gmail.com
Wed Aug 10 15:01:45 NZST 2005


Delphi links the entire DCU into the application. The idea is to keep 
dcu's as concise as necessary, and to remove
unneeded ones from the uses clauses. with Optimization turned on when 
you compile a dcu it will remove any
lines of code that are perceived as unnecessary to the application.

John Bird wrote:

>A question about how Delphi works...
>
>1 - Main question is about Library routines.  I maintain a library unit with
>a lot of (non-visual) procedures and functions for various miscellaneous
>tasks - date formatting, number formatting, file i/o etc.  Some 70 routines
>and growing.  Now when I use this unit in a program, does (a) everything in
>the unit get compiled and linked in, or (b) is it smart enough just to get
>just the code called (including library procedures called from another
>called from the program).  I have come from another language where it always
>did (b), hoping Delphi is as smart.  If not, then I need to separate my
>library procedures into smaller logically related units rather than one
>humungous big unit with everything in it to avoid the programs getting
>bloated with non-used code.
>
>John B
>______________________________________________
>Delphi mailing list
>Delphi at ns3.123.co.nz http://ns3.123.co.nz/mailman/listinfo/delphi
>
>
>_______________________________________________
>Delphi mailing list
>Delphi at ns3.123.co.nz
>http://ns3.123.co.nz/mailman/listinfo/delphi
>
>  
>


More information about the Delphi mailing list