#236 Remove OWL5_COMPAT from trunk

[Ognyan Chernokozhev]

As discussed in [feature-requests:#235], there is no reason to keep OWL5_COMPAT option in the trunk going forward.

The recommended path for upgrading from OWL 5 is to first update to OWLNext 6.44, resolve all issues, remove the dependency on OWL5_COMPAT, and then move forward.

See Upgrading from OWL | Recommended upgrade path.

For more on OWL5_COMPAT, see OWL Compatibility Build Modes.

[Ognyan Chernokozhev]

As a part of this cleanup, we should also remove the OWL_SUPPORT_BWCC and OWL_SUPPORT_CTL3D code - which was compiled only in OWL5_COMPAT mode anyway.

[Vidar Hasfjord]

Hi Ognyan,

Good work on implementing this in [r6466] and [r6467]! To make sure builds fail if OWL5_COMPAT is used (e.g. by current or older OWLMaker versions), I have made further OWL5_COMPAT and compatibility mode changes in [r6472].

[Vidar Hasfjord]

Also have a look at "Remove TAppDictionary" [feature-requests:#19]. It stems from Win16, and has no purpose in Win32, I think.

[Vidar Hasfjord]

The old implementation of response tables, only active in the obsolete OWL5_COMPAT build mode, has now been removed [r6772]. The code now always uses the new implementation with event handler signature checking. See Windows Message Dispatch in OWLNext.