🚀 go-pugleaf

kmh@leland.Stanford.EDU (khanhmy hoang) writes:


>	My program using Borland's OWL (statically linked) worked perfectly
>	in Windows 3.0 and 3.1 when built using BC++ 3.0.
>	When built using BC++ 3.1, the program crashes in Windows 3.0 but
>	still works fine in Windows 3.1.

>	I did define WIN30 during compilation, and this should give me backward
>	compatibility. But this is not what I get.

>	Specifically, the Attr data member of a TListBox control has valid
>	values in Windows 3.1 but has 0's in Windows 3.0 (as watched in TDW).
>	Apparently Attr has an invalid address in 3.0 and this gives me the UAE.

>	Your help is much appreciated.

I've been having weirdness with TC++ 3.1 for 3.0 windows but not on the
TListBox. All works perfectly well on 3.1 windows. Some MetaFile calls
and some BitBlt's just unexplainably UAE. The problem is more releated to
3.0 being less robust than 3.1. I suspect perhaps in both yours and my case
that there is a minor bug in our code (or windows 3.0) that is floating around
and a different compiler can hide or show it up.