Re: [boost] Win32/Borland failures

2002-12-16 Thread Beman Dawes
At 06:59 AM 12/13/2002, John Maddock wrote: No, and the toolset hasn't changed recently either. __BORLANDC__ is reporting 0x0560 as the version, and bcc32 at the command line reports version 5.6. The CD-ROM it came on says C++ Builder 6 Personal. I checked the web site, and don't see any

Re: [boost] Win32/Borland failures

2002-12-13 Thread John Maddock
No, and the toolset hasn't changed recently either. __BORLANDC__ is reporting 0x0560 as the version, and bcc32 at the command line reports version 5.6. The CD-ROM it came on says C++ Builder 6 Personal. I checked the web site, and don't see any service packs available for download. There is

Re: [boost] Win32/Borland failures

2002-12-13 Thread John Maddock
No, and the toolset hasn't changed recently either. __BORLANDC__ is reporting 0x0560 as the version, and bcc32 at the command line reports version 5.6. The CD-ROM it came on says C++ Builder 6 Personal. I checked the web site, and don't see any service packs available for download. I still

Re: [boost] Win32/Borland failures

2002-12-12 Thread John Maddock
The Win32 regression tests are working again, but there are a lot of new Borland failures. See http://boost.sourceforge.net/regression-logs/cs-win32-diff.html It looks like some change to a commonly used library is causing an assertion to fail in the Borland compiler. Strange: I tried

[boost] Win32/Borland failures

2002-12-11 Thread Beman Dawes
The Win32 regression tests are working again, but there are a lot of new Borland failures. See http://boost.sourceforge.net/regression-logs/cs-win32-diff.html It looks like some change to a commonly used library is causing an assertion to fail in the Borland compiler. There are also some new

Re: [boost] Win32/Borland failures

2002-12-11 Thread Yitzhak Sapir
On Wed, 11 Dec 2002, Beman Dawes wrote: The Win32 regression tests are working again, but there are a lot of new Borland failures. See http://boost.sourceforge.net/regression-logs/cs-win32-diff.html It looks like some change to a commonly used library is causing an assertion to fail in the