- Boost - lists.boost.org

TT_AUX_IS_CONVERTIBLE_FROM_FLOAT_CV_SPEC in type_traits/is_convertable.hpp
by Aaron W. LaFramboise 26 Jul '04

26 Jul '04

These three lines near the end of boost/type_traits/is_convertable.hpp: TT_AUX_IS_CONVERTIBLE_FROM_FLOAT_CV_SPEC(float) TT_AUX_IS_CONVERTIBLE_FROM_FLOAT_CV_SPEC(double) TT_AUX_IS_CONVERTIBLE_FROM_FLOAT_CV_SPEC(long double) don't compile on GCC 3.4.1 when -pedantic is specified. This is actually sort of strange, because it compiles without warnings when -std=c++98 -Wall -W are specified, and -pedantic itself is not supposed to generate errors, only warnings. So, there is probably at least a GCC bug here. Does anyone have any idea what this is about? $ g++ -pedantic -I../boost -c stuff.cpp In file included from stuff.cpp:1: ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: redefinition of `struct boost::is_convertible<float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: previous definition of `struct boost::is_convertible<float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: redefinition of `struct boost::is_convertible<const float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: previous definition of `struct boost::is_convertible<const float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: redefinition of `struct boost::is_convertible<volatile float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: previous definition of `struct boost::is_convertible<volatile float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:274: error: redefinition of `struct boost::is_convertible<const volatile float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:274: error: previous definition of `struct boost::is_convertible<const volatile float, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: redefinition of `struct boost::is_convertible<double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: previous definition of `struct boost::is_convertible<double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: redefinition of `struct boost::is_convertible<const double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: previous definition of `struct boost::is_convertible<const double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: redefinition of `struct boost::is_convertible<volatile double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: previous definition of `struct boost::is_convertible<volatile double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:275: error: redefinition of `struct boost::is_convertible<const volatile double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:275: error: previous definition of `struct boost::is_convertible<const volatile double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: redefinition of `struct boost::is_convertible<long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: previous definition of `struct boost::is_convertible<long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: redefinition of `struct boost::is_convertible<const long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: previous definition of `struct boost::is_convertible<const long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: redefinition of `struct boost::is_convertible<volatile long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: previous definition of `struct boost::is_convertible<volatile long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: long, short, signed or unsigned used invalidly for `type name' ../boost/boost/type_traits/is_convertible.hpp:276: error: redefinition of `struct boost::is_convertible<const volatile long double, int64_t>' ../boost/boost/type_traits/is_convertible.hpp:276: error: previous definition of `struct boost::is_convertible<const volatile long double, int64_t>' Pentium 4 on Windows XP Pro gcc 3.4.1 on mingw32 binutils 2.15 mingwrt 3.3 Thanks for your attention, Aaron W. LaFramboise

2 2

Re: [boost] Re: [test] regression with latest change tolibs/test/src/test_tools.cpp
by JOAQUIN LOPEZ MU?Z 26 Jul '04

26 Jul '04

Hi Gennadiy ----- Mensaje original ----- De: Gennadiy Rozental <gennadiy.rozental(a)thomson.com> Fecha: Domingo, Julio 25, 2004 9:55 pm Asunto: [boost] Re: [test] regression with latest change tolibs/test/src/test_tools.cpp > > FYI, latest changes to the aforementioned > > file seem to break things for msvc-stlport, > > as shown for instance at: > > Dave tried to use "using namespace std" solution. It's already > fixed in cvs. > Thanks for the quick response! Let's see if this fixes things up in the next testing cycle. Best, Joaquín M López Muñoz Telefónica, Ingectigación y Desarrollo

3 5

Re: [boost] [Important For All Boost Contributors] BSL Status Update
by Stephan T. Lavavej 26 Jul '04

26 Jul '04

[Stephan T. Lavavej] > I ran it on all of the directory names in libs, in current > Boost CVS, except for CVS, python, and serialization - the > last two gave errors. [Doug Gregor] > Thanks! Sure. I had to copy a .css file to a different directory to get bcp to work in the first place. I don't know why bcp was complaining about python and serialization, and I didn't know enough to hack around it. [Stephan T. Lavavej] > The following people ARE in blanket-permission.txt, but have > used these alternate names in Boost code. > Doug Gregor [Doug Gregor] > This one should now be fixed... Great! [Stephan T. Lavavej] > * "Files that could be converted to the Boost Software > License" should be. There are a lot of files there. [Doug Gregor] > I'll see if I can come up with a program to do this > automagically. We have to be _very_ careful with this, > though. Ok. I agree, that's something that can't be screwed up. [Stephan T. Lavavej] > I don't think "boost org" is a real organization. [Doug Gregor] > I'll take care of this. Awesome! [Stephan T. Lavavej] > * The following organizations (or people with really, really > weird names) hold copyrights to non-BSL libraries. They > should be contacted. > Free Software Foundation Inc [Doug Gregor] > They're not going to agree to the BSL, that's for sure :) The Boost site says that all libraries in Boost, even those not under the BSL, conform to Boost licensing requirements (which excludes the GPL and friends). So the FSF code in Boost shouldn't be under the GPL or any of its derivatives. From my decidedly non-lawyer point of view, the BSL is just a precise statement of the Boost licensing requirements. So the FSF may not be ideologically opposed to BSL conversion. But I don't know what the FSF code in Boost is actually licensed under. > This only affects the Graphviz parser in the BGL, which is > due for a rewrite soon anyway. Ok. This does not personally affect me (I'm real interested in bind and smart_ptr for work), but it should be cleared up. Thanks for looking into some of the [quasi-]organizations I listed. > We should make this a requirement, I think. Agreed. > Probably just a form of license not matched by one of the > regexes in bcp. Easily fixed, with a little time investment. > it might be more useful to have that scorecard showing which > libraries are completely under the BSL. Both are easy enough > to implement. Such a scorecard would be excellent (something to point Microsoft's Big Scary Lawyers at). Thanks for your continuing great work! Stephan T. Lavavej

4 3

additional boost libraries?
by Aleksander Demko 26 Jul '04

26 Jul '04

I, like billions of other developers, have a medium sized project that for various reasons, invented its own thread, io, etc libraries. I'm thinkin of switching over to boost stuff for all my utility needs, but I'm wondering if boost has/possibly will have/is open to the possibility of adding/ or will never have the following facilities: serialization/object persistance (via iostreams) network socket iostreams UUID stuff (sometimes know as GUIDs) interface to dlls/.so loading url parsing (something like the filesystem lib) and, just out of curiosity: xml/html parsing Thanks in advance. -- // scopira.org | ninjacoder.com //

14 25

[program_options] unicode_test regressions for CW8
by Rene Rivera 26 Jul '04

26 Jul '04

Volodya, Did some more investigation and the basic reason for the failure is that the CW8 lexer doesn't do phase 1 translations of the universal character names. So for string like: L"--foo=\u044F", the "\u044F" is translated into 'u'+'0'+'4'+'4'+'F'. The workaround, which should apply to any compiler that doesn't do universal character names, is to use "\x044F" instead: =================================================================== RCS file: /cvsroot/boost/boost/libs/program_options/test/unicode_test.cpp,v retrieving revision 1.2 diff -u -r1.2 unicode_test.cpp --- unicode_test.cpp 26 Jun 2004 11:33:02 -0000 1.2 +++ unicode_test.cpp 24 Jul 2004 14:49:23 -0000 @@ -32,12 +32,12 @@ ; vector<wstring> args; - args.push_back(L"--foo=\u044F"); + args.push_back(L"--foo=\x044F"); variables_map vm; store(wcommand_line_parser(args).options(desc).run(), vm); - BOOST_CHECK(vm["foo"].as<wstring>() == L"\u044F"); + BOOST_CHECK(vm["foo"].as<wstring>() == L"\x044F"); } // Test that unicode input is property converted into @@ -56,7 +56,7 @@ ; vector<wstring> args; - args.push_back(L"--foo=\u044F"); + args.push_back(L"--foo=\x044F"); variables_map vm; store(wcommand_line_parser(args).options(desc).run(), vm); @@ -82,7 +82,7 @@ variables_map vm; store(command_line_parser(args).options(desc).run(), vm); - BOOST_TEST(vm["foo"].as<wstring>() == L"\u044F"); + BOOST_TEST(vm["foo"].as<wstring>() == L"\x044F"); } // Since we've already tested conversion between parser encoding and @@ -100,7 +100,7 @@ ("foo", po::value<string>(), "unicode option") ; - std::wstringstream stream(L"foo = \u044F"); + std::wstringstream stream(L"foo = \x044F"); variables_map vm; store(parse_config_file(stream, desc), vm); =================================================================== Those changes let the test pass on CW8, and they still work on VC7.1. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq

2 1

Re:Re: [boost] Re: serialization:question regarding test
by Robert Ramey 26 Jul '04

26 Jul '04

Aleksey Gurtovoy wrote: >Robert Ramey writes: >> I don't see that this should be a problem. Just follow the instructions in >> the release notes: >> >> a) Download spirit 1.61 from SourceForge.net to a local directory. On my >> machine its c:/spirit161 >> >> b) Define (export) environmental variable SPIRIT_ROOT=c:/spirit161. >> >> The build/test jamfile set up is sensitive to the SPIRIT_ROOT >> variable and will put it in the include path for those systems that >> are known to require it. Right not that is msvc 6.0 and all tested >> borland compilers. Other compilers just work with the latest >> version of spirit from the CVS Tree. This works on my system >> without any other special adjustments other than the above. So I'm >> asking that the testers set up their environment as above before >> running the tests. I don't think that's an unreasonable request. >It's not unreasonable. However, before we do that, we at least need to >figure out how to indicate in the reports that the MSVC 6.0 results >are in fact produced by compiling against something else than the >main trunk. This kind of mark-up is not currently supported and would >require a bit of coding that I'm afraid we don't have resources for at >the moment. This is explained in the serialization documentation. I wouldn't think this is interesting for the notes markup. I don't see that the above issue has any relationship at all with the question of notes markup. Regarding markup. As far as I can tell, there is no simple way to specify a note that a applies to all tests for a given toolset. E.G. All serialization tests that depend upon wide character i/o under gcc/cygwin as wide char i/o isn't supported there. E.G. All tests which depend up export on borland compilers fail. E.G. All tests for msvc which use more than one archive class in the same code module fail. These issues are addressed in the library documentation. I don't see an easy way to fit them into the notes system. Robert Ramey

3 5

[test] regression with latest change to libs/test/src/test_tools.cpp
by JOAQUIN LOPEZ MU?Z 26 Jul '04

26 Jul '04

FYI, latest changes to the aforementioned file seem to break things for msvc-stlport, as shown for instance at: http://tinyurl.com/6br7t [format] http://tinyurl.com/6xt58 [minmax] http://tinyurl.com/48hd6 [multi_index] Joaquín M´López Muñoz Telefónica, Investigación y Desarrollo

3 2

Re: [boost] Re: [test] regression with latest change tolibs/test/src/test_tools.cpp
by JOAQUIN LOPEZ MU?Z 26 Jul '04

26 Jul '04

----- Mensaje original ----- De: "Victor A. Wagner Jr." <vawjr(a)rudbek.com> Fecha: Domingo, Julio 25, 2004 11:54 pm Asunto: Re: [boost] Re: [test] regression with latest change tolibs/test/src/test_tools.cpp [...] > Also, I now have the vc8.0 beta and would be happy to add those > to my > testing if I only knew how to go about adding a toolset. Any > assistance > would be greatly appreciated. > Aleksey explains the procedure at: http://www.meta-comm.com/engineering/regression_setup/instructions.html Good luck, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

run-fail on non-Wondows platforms
by Gennadiy Rozental 25 Jul '04

25 Jul '04

What up with subject? Why all Boost.Test unit tests fail? Gennadiy.

1 0

WARNING: many changed files...
by Rene Rivera 25 Jul '04

25 Jul '04

I just finished cleaning up *all* occurrences of TABS and END-OF-LINE problems. Your next update will contain many file changes (all whitespace). And *PLEASE* to not introduce more of these errors. It's somewhat of a pain to fix the TAB errors :-( -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq

1 0