BS>> Are you sure ?  The way that the most trivial program that uses a 
BS>> visualcomponent jumps to at least 250k or so in size certainly 
BS>> creates theimpression that the Turbo Pascal smart linker has become 
BS>> an extinct species.
SB> Butting in and adding my 2 cents ....You must understand that in order 
SB> for an application to create a simple window and all the stuff that makes 
SB> it work as it does, requires a reasonable amount of code. A comparable C 
No it doesn't. 8-9K of object code (maybe 6K if you write in asm) plus dialog 
templates. __All__ the object-oriented Windows languages add a pretty vast 
bloat to executable size when coding trivial, or at least small programs.
SB> program using the MFC or OWL might have a small exe but would require a 
big
MFC and OWL are both really, really special (and unusually bad) examples 
though, mainly because the operating environments they are designed to use 
don't have an OO design paradigm, and so the runtime library has a lot of 
work to do.
 
SB> mentioned in the past a few times, it would be nice to have the option to 
SB> distribute a DLL or set of DLLs for use by Delphi apps and then compile 
SB> your apps to use those DLLs instead of putting reusable code in each exe. 
You want such an option ? I am already writing a shareware registration DLL 
(well, more than for shareware really, it's a general purpose licensing API). 
Win16 version is in beta as we speak. The Win32 and OS/2 Presentation Manager 
versions will follow after my exams.
I have plans on the drawing board for a couple of other programmer aid type 
DLLs and would be open to suggestions from others as to what I should be 
writing.
-- Lewin A.R.W. Edwards [Team OS/2]  Tel 0419320415 * 0412809805 * 0414927056
--- MsgedSQ/2 3.35
---------------