🚀 go-pugleaf

statters@csaadel.adl.csa.oz.au (Steve Tattersall) writes:

>If the dynamic link option is chosen for the Borland run-time,
>OWL and class libraries, the programme fails to terminate
>properly.

>A GA fault is reported in the run-time DLL and then many errors
>dialogs appear with random characters in them.

>All code has been built using windows 3.0 resources and headers.
Steve,
yes I know this one. Here is, what the Borland guy on CIS told me:
OWL.DLL does some cleaning up in its WindowExitProcedure WEP. There it
deletes an instance of the TMODULE class. This happenes in the
MODULE.CPP source file (near the end of the file). However, when
Win3.0 calles the WEP of a DLL, the stack it allows is so small, the
WEP MUST NOT USE API calls (sounds ridiculous, does it not). Win3.1
has corrected the problem, so the new OWL31 tries to be nice and
cleans up the memory it needed. But if you want to use the OWL.DLL under
Win3.0, you'll have to remove the "delete Module;" line, since the delete
call tries to use some API function.
After you rebuilt the OWL31.DLL, everything should work ok.

>Linking the code with static libraries, the code fails to start under
>WIN-OS2 (the not supported / not recognised error).
Concerning this, there is a switch under Options (I think) Resource, which
distiguishes btw 3.0 and 3.1 Applications. Also you probably should
define WIN30 rather than WIN31;STRICT, when using the OWL.

Have fun.

-Hajo
---
--------------------------------------------------------------------------
Hans-Jochen Kirchhoff | hmkirchh@cip.informatik.uni-erlangen.de
> No signature today  | CompuServe 100024,712