> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Grant Black
> Sent: Wednesday, 12 May 1999 10:02
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: Why Delphi is Better Than VB
snip
> The other thing about VB that gets me is that it has a total reliance on
> external VBX/OBX/COM objects - this bite developers in support problems
> as if any of the DLL's change (and they do) then your app can grind to a
> halt, (see the problems with ComCtrl32 alone).� With VCL being bound up
> in the EXE then you app is more self-contained and more likely to keep
> running over the years.
Ah but... a lot of VCL stuff is dependent on DLL calls into the Win32 API.
The Comctl32 thing broke the Delphi TImageList component a few years back.
Those DLLs are changing all the time. All that you have bound up into your
app is the Delphi code that calls those APIs. The APIs can and do change all
the time. Have a look at Windows.pas and you will find it consists mostly of
calls to external DLLs, there is very little actual Delphi code in there.
snip
============================================
Patrick Dunford, Christchurch, NZ
http://patrick.dunford.com/
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
