[DUG] manually process Windows messages

[Jolyon Smith]

I wouldn't expect that at all.  I forget the details of why, but using the
Forms unit unavoidably drags in a whole host of VCL code.  This is easily
tested, just try compiling:

 

program Vacuum;

begin

end.

 

And you get an EXE of 22KB.  Simply adding a "uses Forms;", even without
referencing anything from the Forms unit in the "code" and your equally
non-functional vacuum.exe "explodes" to 382KB (BDS2006).

 

Having said that, 382KB is not exactly excessive "bloat" in my book.

 

So my question for the original poster is what criteria is it that demands
that the executable absolutely has to avoid this overhead?

 

 

From: delphi-bounces at delphi.org.nz [mailto:delphi-bounces at delphi.org.nz] On
Behalf Of John Bird
Sent: Tuesday, 26 January 2010 9:55 a.m.
To: NZ Borland Developers Group - Delphi List
Subject: Re: [DUG] manually process Windows messages

 

I would expect if you specify Forms (to get Application.ProcessMessages) and
only call that and nothing else from Forms then you will only get what
functions are needed linked into your application - I suggest you try it and
see how much bigger it makes the application.

 

John

 

I've looked at what Application.ProcessMessages does but I'm not sure what I
need to get this working.  Any thoughts appreciated, or some code J.

 

Thanks,

Ross.

Tauranga.


  _____  


_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi at delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-request at delphi.org.nz with Subject:
unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20100126/13f90743/attachment-0001.html