- Boost - lists.boost.org

[range] CW on MacOSX failures...
by Rene Rivera 07 May '05

07 May '05

Could someone explain what the intent of this change is: http://cvs.sourceforge.net/viewcvs.py/boost/boost/libs/range/test/string.cp… http://tinyurl.com/8efhq Specifically the "#define _MSL_USING_NAMESPACE 1"? That is causing duplicate def errors, as this is supposed to be an internal MSL macro. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

1 0

[numeric/conversion] CW and VC8 fixes.
by Rene Rivera 07 May '05

07 May '05

All the tests for this library should now pass for all CodeWarrior versions. I also fixed two files with bad EOLs, which will likely fix the problems with VC8. Note.. if you see this kind of error on the VC8 logs: error C4335: Mac file format detected: please convert the source file to either DOS or UNIX format It's because of EOLs problems also reported at: http://www.boost.org/regression-logs/inspection_report.html -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

1 0

Re: [boost] Re: BOOST_FOREACH review results
by brangdon＠cix.compulink.co.uk 07 May '05

07 May '05

In-Reply-To: <d5d7h5$3cp$1(a)sea.gmane.org> gennadiy.rozental(a)thomson.com (Gennadiy Rozental) wrote (abridged): > While this is discussible position, I did not see you prove you > point enough to reject a submission. As I said, that wasn't my reason for voting against the proposal. However, I'm content with the final result; I don't expect or want to overturn it. -- Dave Harris, Nottingham, UK.

1 0

[date_time] CodeWarrior fixes.
by Rene Rivera 07 May '05

07 May '05

I put in some fixes to clear out some of the CodeWarrior regressions. Only four types of problems still exist: 1. There are DLL tests that use std::locale, directly or indirectly I don't know, but they should be marked as expected-to-fail. 2. There are tests that fail because boost.serialization lib fails to build. I'll eventually get to checking why that doesn't build. 3. There are two tests that now compile, but fail at runtime with an access violation. From previous experience it looks like accessing a vtable method through a NULL pointer. The tests are the two *_time_input_facet. 4. There's an unexplained compiler confusion at: boost\date_time\date_parsing.hpp:262: data type is incomplete Possibly the compiler is trying to instantiate too early? Don't really know. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

2 1

[Test] Thread-safety
by Cliff Green 07 May '05

07 May '05

Silly me - I should have looked in the Boost.Test Open Issues page a couple of days ago instead of wasting my time trying to solve some multi-threading problems in my own code. So a couple of enhancement requests (for Gennadiy, or appropriate person): 1. Please state clearly in the Boost.Test documentation that it is not thread-safe. I looked all through the pages (both the current release and the 1.31 release) but the only place I find mention of thread-unsafety is in the Open Issues page. The FAQ page would also be a good place to mention Boost.Test thread-unsafety, besides the main page (and places like Usage Recommendations, Examples, Compilation, etc). 2. Please consider adding thread-safeness to the Boost.Test libraries. I know this is not a simple request, and there may be other priorities ... but many of my (and my team's) unit tests are multi-threaded, and it's a shame to not be able to use Boost.Test (or even know which, if any, parts are thread-safe). It's a nice testing framework, IMO. Note that I don't need the whole library itself to be threaded, just to be able to do things like BOOST_MESSAGE and BOOST_EQUAL within my own testing threads. (I'll offer whatever help I can provide, within the constraints of my available time.) Many thanks! Cliff

4 4

Re: [boost] BOOST_FOREACH review results
by brangdon＠cix.compulink.co.uk 07 May '05

07 May '05

In-Reply-To: <989aceac050505060373e68a1(a)mail.gmail.com> caleb.epstein(a)gmail.com (Caleb Epstein) wrote (abridged): > > What about the name? Shouldn't it be "BOOST_FOR_EACH"? > > Why? Because of the distinct English words? Yes. And for consistency with other C++ macros, algorithms and keywords. I've argued at greater length in the other thread. -- Dave Harris, Nottingham, UK.

5 5

Re: [boost] Singleton Review: GCC compiler errors
by Jason Hise 06 May '05

06 May '05

Sorry about the duplicate messages, thunderbird seemed to be having a problem. Hoping it's fixed now. Jason Hise wrote: > Tom Brinkman wrote: > >> Was the "singleton" library tested on GCC. I'm getting many compiler >> errors on 3.34. > > It was a while back, but many changes have been made since then. I'll > see if I can track down a copy of gcc to try compiling with it myself. Actually, now that I'm looking into it it appears that Dev C++ uses a port of GCC by default, and I have successfully tested the latest version with Dev C++, getting no warnings or errors. What error messages are you getting? -Jason

3 2

[test] PATCH: putenv usage incorrect
by Caleb Epstein 06 May '05

06 May '05

http://tinyurl.com/72sj8 This test is failing on numerous platforms, some for the fact that "putenv" takes a non-const char* (Linux, Solaris, perhaps others). Attached is a patch for environment.ipp which changes it to use the setenv function on non-Windows systems. I believe this is a POSIX standard function (via BSD). I think this cleans up the code a bit, removing the raising of getenv/putenv into namespace std, when they are I think clearly non-std functions. -- Caleb Epstein caleb dot epstein at gmail dot com

3 6

[property_map] test program fix.
by John Maddock 06 May '05

06 May '05

The following fix gets the property_map test that's currently failing with several high-quality compilers, building OK (at least with vc7.1, I can't test with MWCW, but that compiler has the same issue with the existing test so it should fix it). Is this OK to commit? John. diff -r1.1 dynamic_properties_test.cpp 110c110 < BOOST_CHECK(get<std::string>("nada",props,std::string("3.14")) == "pi"); --- > BOOST_CHECK(get("nada",props,std::string("3.14")) == "pi");

1 0

[Integer] Mac OS X: WCHAR_MIN != std::numeric_limits<wchar_t>::min()
by Douglas Gregor 06 May '05

06 May '05

The title says it all: the Mac OS X system headers are inconsistent about the minimum value of a wchar_t. The C++ <limits> header has it right, but the definition of WCHAR_MIN in <cwchar>/<wchar.h> is wrong (0). If there are no complains, I'm going to commit the following patch. I don't believe this will affect CodeWarrior on the Mac, but I can't test against it. Index: integer_traits.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/integer_traits.hpp,v retrieving revision 1.26 diff -u -r1.26 integer_traits.hpp --- integer_traits.hpp 17 Dec 2004 11:56:15 -0000 1.26 +++ integer_traits.hpp 6 May 2005 15:46:36 -0000 @@ -88,7 +88,9 @@ template<> class integer_traits<wchar_t> : public std::numeric_limits<wchar_t>, -#if defined(WCHAR_MIN) && defined(WCHAR_MAX) + // Don't trust WCHAR_MIN and WCHAR_MAX with Mac OS X's native + // library: they are wrong! +#if defined(WCHAR_MIN) && defined(WCHAR_MAX) && !defined(__APPLE__) public detail::integer_traits_base<wchar_t, WCHAR_MIN, WCHAR_MAX> #elif defined(__BORLANDC__) || defined(__CYGWIN__) || defined(__MINGW32__) || (defined(__BEOS__) && defined(__GNUC__)) // No WCHAR_MIN and WCHAR_MAX, whar_t is short and unsigned: Doug

1 0