Re: BDS2006 exe sizes
- From: "Maarten Wiltink" <maarten@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 26 Feb 2006 10:28:02 +0100
"J French" <erewhon@xxxxxxxxxx> wrote in message
news:44016c31.5759669@xxxxxxxxxxxxxxxxxxxxxxx
On Sat, 25 Feb 2006 12:38:48 +0100, Hans-Peter Diettrich[...]
<DrDiettrich@xxxxxxxxxxx> wrote:
A 32 bit console application uses Windows APIs instead of interrupts.
The capabilities of these APIs grow with every new Windows version,
so that the libraries also must grow, in order to make the new console
etc. functionality available to applications.
Really ?
The APIs are just declarations, mostly in the windows unit
- also the compiler strips out code that it knows is not used
Yes, really. Every library import is another entry in the import table.
The compiler doesn't care ("Hello world!"), but the linker gets accused
of yet more bloat.
[...]
I like to envisage the .NET framework as a reversion to MS's VB
runtime DLL that contains a PCode interpreter (and I suspect elements
of a JIT compiler)
By and large correct. The JIT compiler is mandatory and partly not
really JIT anymore, it preprocesses the entire RTL when you install
the framework. (It took _forever_ to install .Net 2.0 on a K6-II 350.)
Not a bad design, especially for portability, but not the original
Delphi concept.
Tell me again. What does the P in P-code stand for?
Groetjes,
Maarten Wiltink
.
- Follow-Ups:
- Re: BDS2006 exe sizes
- From: J French
- Re: BDS2006 exe sizes
- References:
- BDS2006 exe sizes
- From: Ian
- Re: BDS2006 exe sizes
- From: Uffe Kousgaard
- Re: BDS2006 exe sizes
- From: Ian
- Re: BDS2006 exe sizes
- From: Uffe Kousgaard
- Re: BDS2006 exe sizes
- From: Ian
- Re: BDS2006 exe sizes
- From: Hans-Peter Diettrich
- Re: BDS2006 exe sizes
- From: J French
- BDS2006 exe sizes
- Prev by Date: Re: BDS2006 exe sizes
- Next by Date: Re: BDS2006 exe sizes
- Previous by thread: Re: BDS2006 exe sizes
- Next by thread: Re: BDS2006 exe sizes
- Index(es):