> That's unfair. If performance were everything we wouldn't be using Delphi
> component wrappers when we could make WinAPI calls directly. And we
> wouldn't be making WinAPI calls when we could hit the hardware directly.
> Both of those layers slow things down in a similar fashion to having a
> virtual machine layer, but they provide powerful benefits. So does the Java
> VM.
> None of us should care much about a theoretical performance penalty until we
> can see it. Classes, Events, Properties, Messages: all carry a performance
> penalty.
This is true - much of Delphi is built on non-optimal list structures for situations
where
ordered-balanced trees tuned to the particular key-type might be better suited. This is
the world of compromise - devloped quicker and simpler and more reusable versus
customised tweaked and tuned nibbled down to the last bit and clock-cycle style
development. Identify bottlenecks and address them, the VM is not itself a large
bottleneck - mis-application certainly is.
--
Aaron Scott-Boddendijk
INTAZ Limited
+64 7 838 3371 Voice
+64 7 838 3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
