----- Original Message -----
From: "Florian Klaempfl" <[EMAIL PROTECTED]>
To: "FPC developers' list" <fpc-devel@lists.freepascal.org>
Sent: Saturday, May 28, 2005 11:20 PM
Subject: Re: [fpc-devel] don't you think it'stime
toupdatedelphimodecompatibility? - IDispatch, implements
Besides I find that FPC 2.0 makes the executables just to big.+
C:\fpc>type test1.pp
begin
writeln('Hello world');
end.
...
28.05.2005 23:14 25.600 test1.exe
28.05.2005 23:14 11.264 test1.exe
...
IIRC Delphi creates 16 kB something.
And did you try UPX on delphi-created executables? You cannot compare
something that's not compressed with something that IS compressed - that
makes no sense.
Other thing is that the Hello, world! app is NOT using anything. AFAIK this
is not the way the apps are written :). Normally you will link the SysUtils,
Classes, and under windows the Windows unit what makes the whole thing a lot
bigger than under Delphi. A simple app that's using SysUtuils under FPC is
2x the size of the same app compiled with delphi. The other example is the
Classes unit. I agree, that after using UPX the code differs only 10% (FPC
is still 10% bigger) but using UPX is not recomended ie. for DLLs. Going on
with this and compiling the simplies FCL-based application differs really
strongly from the same done under delphi. I know you can do all of the GUI
thing using base interface for GUI (Win32 API for example) but this doesn't
solve prtability issues. I don't like my executables grow beyond some
certain point and achieving this point after adding 10 controls to my GUI
app is not acceptable. In addition comparing the sources of VCL and FCL they
don't differ that much and the source isn't that much bigger so by this kind
of differences the problem must lie with compiler/linker.
Matthias
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
