Maybe a __BORLANDC__LATEST could be defined in the compiler config headers rather than embedding version numbers all over the place (I don't know how many places 0x56x is used explicitly, so this may not be necessary)
Cheers
Russell
Edward Diener wrote:
I have noticed that the 1.30 release does not seem to be aware of the SP4 update to BCB6 and am wondering if anybody has tracked changes that need to be made to 1.30 because of this release. In particular the __BORLANDC__ number for the SP4 release is 0x564 and I have noticed a number of files where tests were being made against __BORLANDC__ numbers of 0x560 ( the original BCB6 release ), 0x561 ( BCB6 SP1 I believe ), and even 0x562 ( BCB6 SP2 I believe ). Of course a number of these tests were <=, <, >=, or > comparisons and I am wondering if I have to change any of these in my own private copy of Boost 1.30 in order to work correctly with BCB6 SP4, and what changes need to be made.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
