[detail] utf8 patch for Borland 2006

Not sure who is maintainer of this file? Anyway, following patch is a little rough, not testing on compiler version, but is required for the current Borland compiler and the Dinkumware libraries it ships with. Fixing this should fix tests across a few libraries: cvs diff -u -wb -- boost\detail\utf8_codecvt_facet.hpp (in directory E:\sourceforge\devel\boost\) Index: boost/detail/utf8_codecvt_facet.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/detail/utf8_codecvt_facet.hpp,v retrieving revision 1.3 diff -u -w -b -r1.3 utf8_codecvt_facet.hpp --- boost/detail/utf8_codecvt_facet.hpp 20 Jan 2006 16:53:30 -0000 1.3 +++ boost/detail/utf8_codecvt_facet.hpp 21 Jan 2006 19:29:24 -0000 @@ -92,7 +92,7 @@ namespace std { #if defined(__LIBCOMO__) using ::mbstate_t; - #elif defined(BOOST_DINKUMWARE_STDLIB) + #elif defined(BOOST_DINKUMWARE_STDLIB) && !defined(__BORLANDC__) using ::mbstate_t; #elif defined(__SGI_STL_PORT) #elif defined(BOOST_NO_STDC_NAMESPACE) ***** CVS exited normally with code 1 ***** -- AlisdairM

Anyway, following patch is a little rough, not testing on compiler version, but is required for the current Borland compiler and the Dinkumware libraries it ships with. Fixing this should fix tests across a few libraries:
Those look pretty uncontroversial to me, you could probably just go ahead with those. John.

John Maddock wrote:
Those look pretty uncontroversial to me, you could probably just go ahead with those.
OK, committed that one. I'm holding fire on the other two until someone else says 'yes', or the release deadline looms! -- AlisdairM
participants (2)
-
AlisdairM
-
John Maddock