Re: local to screen

"Jamie" <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx> wrote in message
news:I9Cjh.544$Cy1.344@xxxxxxxxxxxxxxx
Maarten Wiltink wrote:
"Jamie" <jamie_ka1lpa_not_valid_after_ka1lpa_@xxxxxxxxxxx> wrote in
message
news:Vvwjh.401$Yz7.322@xxxxxxxxxxxxxxx

The Vcl is just a simple wrapper for API calls in windows ...

It most certainly is not. That's the Windows unit.

The VCL is a class library that organises wrapper classes, original
controls, and supporting classes into a consistent hierarchy that
was very much not inherent in the original WinAPI calls and Windows
messages.

excuse me!
The VCL are wrappers for Windows API's
how they are organize makes no differences, at the end, anything
that requires your PC to display, accept input, access hardware
requires you to call API's.
The VCL is just a pile of over head that simply ends up
communicating with the API system.
The term wrapper has nothing to do with what type of code is
being used to perform this. It simply means the API code that is
being used in the background is not forcing the coder to deal
directly with it and most likely is aiding in it's use of it.

The VCL is implemented on top of win32. That is little more than an
implementation detail.

The class hierarchy of TObject, TPersistent, TComponent, TControl is
not dependent on it. The ideas of making TPersistents Assign-able and
the ownership and streaming schemes for TComponents were not prompted
by anything in Windows.

The VCL is not a mere wrapper for WinAPI calls. I dare you to describe
TStringList, TStream, TCustomForm.OnCreate, TCollection.ItemClass, in
those terms. I think you'll find you can't. Brushing all those things
off as 'overhead' is doing them an injustice. If they really make no
difference, you'd be just as productive programming in Assembly.

The term wrapper has a meaning that is much more restriced than you
apparently wish to make it. A virtual machine may technically be a
wrapper, but one that introduces completely new concepts to hide the
old ones will never be a _simple_ wrapper. Your exact words, my
emphasis.

Groetjes,
Maarten Wiltink


.

Relevant Pages

  • Re: local to screen
    ... That's the Windows unit. ... The VCL is a class library that organises wrapper classes, ... The VCL are wrappers for Windows API's ... The term wrapper has nothing to do with what type of code is being used to perform this. ...
    (alt.comp.lang.borland-delphi)
  • Re: local to screen
    ... That's the Windows unit. ... The VCL is a class library that organises wrapper classes, ... The VCL are wrappers for Windows API's ... The term wrapper has nothing to do with what type of code is being used to perform this. ...
    (alt.comp.lang.borland-delphi)
  • Re: local to screen
    ... That's the Windows unit. ... The VCL is a class library that organises wrapper classes, ... The VCL are wrappers for Windows API's ...
    (alt.comp.lang.borland-delphi)
  • Re: Old projects in Delphi 8
    ... "...The VCL can be seen as a wrapper around the Win32 API, ... Framework (or more specifically the Windows Forms classes)..." ...
    (borland.public.delphi.non-technical)