> Can 16 bit DLL's and 32 bit DLL's be used in Delphi 2.0 32 bit
> applications.
> Reason: multi language programming with older 16 bit compilers.

> ben wrote:

> > Can 16 bit DLL's and 32 bit DLL's be used in Delphi 2.0 32 bit
> > applications.
> > Reason: multi language programming with older 16 bit compilers.

> 32 bit DLL, no problem. 16 bit DLL must go through thunk. MSDN has
> info on thunks, in addition, there's an article in Dr. Dobb's
> Sourcebook (March/April I believe) about thunking. Windows NT won't
> allow 32 bit code to call 16 bit code at all, security thing....

> Martin Larsson wrote:

> > ben wrote:

> > > Can 16 bit DLL's and 32 bit DLL's be used in Delphi 2.0 32 bit
> > > applications.
> > > Reason: multi language programming with older 16 bit compilers.

> > 32 bit DLL, no problem. 16 bit DLL must go through thunk. MSDN has
> > info on thunks, in addition, there's an article in Dr. Dobb's
> > Sourcebook (March/April I believe) about thunking. Windows NT won't
> > allow 32 bit code to call 16 bit code at all, security thing....

> Also, if you want to avoid all that thunking poo, you can use the
> WM_COPYDATA windows message to communicate data between 16 and 32
> bit apps.  I show an example of this in Delphi 2 Developer's Guide.

> Steve Teixeira wrote:

> > Also, if you want to avoid all that thunking poo, you can use the
> > WM_COPYDATA windows message to communicate data between 16 and 32
> > bit apps.  I show an example of this in Delphi 2 Developer's Guide.

> Ahhh, spoken like a true businessman trying to plug his book, and
> not the great borland support engineer that he actually is.
> If you're going to use your Borland account, wouldn't it be better
> to actually "help" instead of routing it off to something you wrote?
> I have no problems with you telling somebody to buy your book, just
> not with the Borland flag over your head.