The documentation at
http://www.boost.org/libs/conversion/lexical_cast.htm
appears to make no mention of the whitespace-handling, or the fact
that it can't handle things like lexical_cast("0x16"). It would be
appreciated if these restrictions could be made clear.
regards,
john
__
The generated script contains the lines :
# add the -AA conformance option to CXXFLAGS for HP aCC only
if test $CXX = 'aCC'
CXXFLAGS="-AA $CXXFLAGS"
fi
This fails under "sh configure". Changing to :
if test $CXX = 'aCC'; then
CXXFLAGS="-AA $CXXFLAGS"
fi
fixes it
regards
john
--
"What
The documentation on the site indicates I can use GXX or
GCC_ROOT_DIRECTORY to specify which g++ binary to run. However, these
settings are ignored, and the g++ in my path is used instead.
GCC_ROOT_DIRECTORY=/usr/local/gcc-cvs/ TOOLS=gcc ~/bin/bjam
and other variants show this behaviour.
regar
Just wondering if anyone has been isolating testcases etc. from boost
code for gcc HEAD's new parser. The first problem I came across was :
../../boost/boost/type_traits/is_function.hpp:59: error: expected
class-name
../../boost/boost/type_traits/is_function.hpp:59: error: expected `{'
../../boos
On Fri, Jan 17, 2003 at 11:41:23AM -, John Maddock wrote:
> Is anyone able to connect to
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost ?
Sourceforge viewcvs/anoncvs is offline and looks like it will be for
some unspecified period
regards
john
--
"We're standing there pounding a dea
