| > Pavol recently the same problem. Our solution was to pass | > the char* arguments by value. That should be what the current CVS version | > does. | > | | | Are you sure? I just sync'ed, and the string versions of begin() and | end() still take their arguments by reference. The problem remains. I get the extract below from the CVS. The newest version should be 1.12 for begin.hpp and 1.15 for end.hpp. Do your version match? -Thorsten $ cvs diff -c -r1.11 -r1.12 begin.hpp nesotto@cvs.sf.net's password: Warning: No xauth data; using fake authentication data for X11 forwarding. Index: begin.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/range/begin.hpp,v retrieving revision 1.11 retrieving revision 1.12 diff -c -r1.11 -r1.12 *** begin.hpp 5 Jan 2005 18:19:30 -0000 1.11 --- begin.hpp 20 Jan 2005 22:33:24 -0000 1.12 *************** *** 84,90 **** // string ////////////////////////////////////////////////////////////////////// ! #if BOOST_WORKAROUND(__MWERKS__, <= 0x3204 ) || BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564)) // CW up to 9.3 and borland have troubles with function ordering inline const char* begin( const char* s ) { --- 84,90 ---- // string ////////////////////////////////////////////////////////////////////// ! #if 1 || BOOST_WORKAROUND(__MWERKS__, <= 0x3204 ) || BOOST_WORKAROUND(__BORLAN DC__, BOOST_TESTED_AT(0x564)) // CW up to 9.3 and borland have troubles with function ordering inline const char* begin( const char* s ) {