[fpc-pascal] Re: fpc registry unit
Mark Morgan Lloyd
markMLl.fpc-pascal at telemetry.co.uk
Sat Mar 2 11:44:47 CET 2013
>> Registry is not part of rtl because it's not a base unit??? This is my
>> point it uses 200 other f*** units that aren't really needed!
>>
>> So you are saying if one wants a single 50 line unit & does a complex
>> procedure eg installi ng 10^10 lines of fpc etc then it is simple? And of
>> course you have to do this for every version of fpc you want to use!
>>
>> And, of course as I've seen, the size of the .exe from v2.2.2 cf v2.6.2
>> is twice as large because of all the c*** included by the various uses..
>>
>> This is all simple? Not in my dictionary's definition! Dooooooh
What on earth brought that rant on? Being charitable, I have to assume
that somebody was "tired and emotional".
John: the registry unit is fairly straightforward: it imports four units
in total:
{$ifndef XMLREG}
Windows,
{$endif XMLREG}
Classes,
SysUtils,
inifiles;
The xmlreg unit pulls in various XML stuff which obviously has an
overhead. But where on earth do you get this "200 other units" idea?
If you find a unit that imports something else with no reason (which
will usually cause a compile-time warning), then raise it here or report
it as a bug. Similarly, if you find that smartlinking leaves something
in the executable that should be removed then raise it. Finally, if you
find something in the documentation that you don't understand then raise
it here since if you don't get it then it's probably obscure to other
less-experienced users as well. Most of us won't jump down your throat
unless you start cussing :-/
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
More information about the fpc-pascal
mailing list