JW>  -=> Quoting Michael Douglass to Dean London <=-
JW> 
JW>  DL>Jon Wright from Guidelines Support stated that Guidelines 2.1A is not
JW>  >compatible with BCOS/2 1.5, only 1.01.  This is also true of Watcom 10.0;
JW>  >Because of name mangling, it only works with Watcom 9.5.
JW>  
JW>  DL>Apparently Watcom and Borland changed the way they mangle
names in C++ for
JW>  >Watcom 10.0, BC 4.0, and BCOS/2 1.5.
JW> 
JW>  MD> Well, did Jon say anything about a quick fix?  He has failed to
JW>  MD> respond to my questions concerning this.  If it is a simple rebuild of
JW>  MD> the .LIB files, let us know...  Why would Borland do this and lose the
JW>  MD> backward compatibility?
JW> 
JW>      If true, then no old C++ LIBRARIES (Zinc, Zapp, etc.) would work
JW>      with the new BCOS/2 1.5.  Rule one always have complete source
JW>      for every library that you use or do not use it. Now you know
why .
JW> 
JW>      Anyone - does BCOS/2 1.5 work with your old C++ libraries ?
JW> 

I haven't tried it with BCOS/2 but there are incompatibilities between
BC++ 4.0 and BC++ 3.1. This has to do with the new--and ongoing--ANSI
C++ standards and Borland's stricter compliance with them. I cannot run
code written for 3.1 on 4.0 without a special switch or slightly
rewriting the code.

If 1.0 code will not run on 1.5, my guess is that the problem is with 
the new ANSI standards.

___
 X KWQ/2 1.2e NR X I'm an OS/2 developer...I don't NEED a life!

--- Maximus/2 2.01