- Boost - lists.boost.org

[Boost-bugs] [ boost-Feature Requests-1200940 ] Support for embedded VC++ 4.0
by SourceForge.net 12 May '05

12 May '05

Feature Requests item #1200940, was opened at 2005-05-12 19:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1200940&group_… Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: spinooch (spinooch) Assigned to: Peter Dimov (pdimov) Summary: Support for embedded VC++ 4.0 Initial Comment: Are there any plans to release a version of the smart pointer library that will compile under embedded VC++ 4.0? While trying to resolve the following compiler error: "shared_count.hpp(116) : error C2039: 'type_info' : is not a member of 'std'" I noticed that there are include files referenced in the hpp files that do not exist in the SDK provided with eVC++. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1200940&group_… ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[Boost-bugs] [ boost-Feature Requests-1200890 ] Support for embedded VC++ 4.0
by SourceForge.net 12 May '05

12 May '05

Feature Requests item #1200890, was opened at 2005-05-12 18:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1200890&group_… Category: smart_ptr Group: None Status: Open Resolution: None Priority: 5 Submitted By: spinooch (spinooch) Assigned to: Peter Dimov (pdimov) Summary: Support for embedded VC++ 4.0 Initial Comment: Are there any plans to release a version of the smart pointer library that will compile under embedded VC++ 4.0? While trying to resolve the following compiler error: "shared_count.hpp(116) : error C2039: 'type_info' : is not a member of 'std'" I noticed that there are include files referenced in the hpp files that do not exist in the SDK provided with eVC++. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=357586&aid=1200890&group_… ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Bug in boost 1.32: date_time/microsec_time_clock.hpp
by martin troxler 12 May '05

12 May '05

It is possible, that the following line boost::posix_time::ptime now = boost::posix_time::microsec_clock::local_time(); which invokes template<class time_type> class microsec_clock { static time_type local_time() { timeval tv; gettimeofday(&tv, 0); //gettimeofday does not support TZ adjust on Linux. return create_time(&tv); } static time_type create_time(timeval* tv) { time_t t = tv->tv_sec; boost::uint32_t fs = tv->tv_usec; ::std::time(&t); tm* curr = localtime(&t); .... returns a time with 1s off its correct value. The reason for this bug is the line with ::std::time(&t); that overwrites the second value just a few µs after the call to gettimofday. This new second value is used together with the fs value from gettimeofday. Example: tv from gettimofday: 12345s/999998 µs t from std::time: 12346s resulting time: 12346s/999998 µs !!!! Question: Why this call to std::time? I commented it out and it worked. Regards Martin

2 1

[iostreams] gcc-3.4.4 and amd64 patches
by Jürgen Hunold 12 May '05

12 May '05

Hi ! Please find a patch attached which tries to fix 2 issues: First, signed/unsigned mismatch in boost/iostreams/char_traits.hpp The fix is to change is_good(int) to is_good(std::wint_t) Second, boost/iostreams/filter/symmetric_filter_adapter.hpp contains two template implementations without corresponding definitions. gcc-3.4.x chokes on them. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau * voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover * fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover * hunold(a)ive.uni-hannover.de ! www.ive.uni-hannover.de

2 1

VS 2005 Beta 2 + 1.32
by Gordon Smith 12 May '05

12 May '05

Anyone build 1.32 (gold) with VS 2005 Beta 2? If so how? Thanks, Gordon.

2 3

[Boost-bugs] [ boost-Support Requests-1200700 ] Boost on opteron AMD
by SourceForge.net 12 May '05

12 May '05

Support Requests item #1200700, was opened at 2005-05-12 14:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1200700&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: finte (finte) Assigned to: Nobody/Anonymous (nobody) Summary: Boost on opteron AMD Initial Comment: Hello, I need some help. How can I build boost on solaris 10 opteron amd as a 64-bit libraries? It's no problem to build bjam as 64-bit executables but with boost I failed. Has anybody any ideas? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1200700&group_… ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

[ptr_container] memory usage causes problem with regression tests
by Martin Wille 12 May '05

12 May '05

Hello, for approximately a week now, I'm experiencing crashes when I run the regression tests. Victor told me he also noticed tests consuming unusual amounts of memory. I think I now found the culprit: the ptr_container test suite. This is the second time I notice the kernel run out of memory when once of the ptr_container tests is run. This is a problem for running the tests since the kernel then starts to kill processes. So this needs to get fixed ASAP. The ptr_set test output is: *** glibc detected *** free(): invalid pointer: 0x14347b4c *** Running 1 test case... unknown location(0): fatal error in "test_set": signal: SIGABRT (application abort requested) *** errors detected in test suite "Pointer Container Test Suite"; see standard output for details We need a way of portably specifying and enforcing time and memory limits for tests (it's not the first time I've been hit by tests running wild). We also need the authors of tests to make use of that feature, once we have it. I think displaying the time and memory used by a test in the regression results would be helpful (requires changes to Boost.Build, too, obviously). In this special case, it also would have been helpful if absolute times were printed in the output of Boost.Build, since all I have is the time-stamp from the error messages of the kernel but no way of correlating this time-stamp with the regression tests except for incidentally looking at the screen when the crashes happen. Regards, m

3 7

shared_ptr_test fails on rsi-sol g++ 4
by Peter Dimov 12 May '05

12 May '05

Any ideas why the three use_count() tests: { boost::shared_ptr<int> pi(new int); boost::shared_ptr<void> pv(pi); boost::shared_ptr<int> pi2 = boost::static_pointer_cast<int>(pv); BOOST_TEST(pi.get() == pi2.get()); BOOST_TEST(!(pi < pi2 || pi2 < pi)); BOOST_TEST(pi.use_count() == 3); BOOST_TEST(pv.use_count() == 3); BOOST_TEST(pi2.use_count() == 3); } fail as described here: http://www.meta-comm.com/engineering/boost-regression/cvs-head/developer/ou… http://tinyurl.com/cq7qy ? -- Peter Dimov http://www.pdimov.com

1 2

[polymorphic_downcast]
by Thorsten Ottosen 12 May '05

12 May '05

Hi, is there any reason why we cannot say Base& get_ref(); Derived& boost::polymorphic_downcast<Derived&>( get_ref() ); ? It works with pointers, shouldn't we overload for references? -Thorsten -- Thorsten Ottosen ---------------------------- www.dezide.com http://www.cs.aau.dk/index2.php?content=Research/mi www.boost.org www.open-std.org/JTC1/SC22/WG21/

2 3

[Regression Reports] Test case categorization
by Aleksey Gurtovoy 12 May '05

12 May '05

I'd like to draw library authors' attention to a recent generalization in the explicit markup scheme which allows one to control the grouping of a particular library's test cases in the Boost-wide regression reports, as demostrated here -- http://www.meta-comm.com/engineering/boost-regression/example/developer/lib… (http://tinyurl.com/bdd5u) The generalization is aimed at improving representation of library reports in at least two common situations: 1) "Duplicate" test cases: many libraries have two or more variations of the same test case for different configurations (DLL vs. static linking, char vs. wchar_t, etc.). 2) Test cases covering corner-case/optional/advanced functionality. In both of these cases, it's common to have an explicit markup (or actual failures) painting a group of test cases in a different color for one or more deficient toolsets -- see, for example, Boost.Thread page (http://tinyurl.com/8duf6) Test case categorization allows library authors to reduce the amount of visual clutter in the reports, giving them a more organized/structured look -- ultimately improving visitors' experience. Assigning a category to a test case or a group of test cases is just a matter of specifying the 'category' attribute to the corresponding '<test>' elements in "status/explicit-failures-markup.xml", e.g. <library name="my_library"> <test name="*_dll" category="DLL"/> </library> or <library name="iterator"> <test name="is_convertible_fail" category="Corner-case tests"> <mark-failure> <toolset name="borland"/> <toolset name="borland-5_6_4"/> <toolset name="msvc"/> <toolset name="vc7"/> <note refid="2"/> </mark-failure> ... As always, feedback is more than welcome. Enjoy, -- Aleksey Gurtovoy MetaCommunications Engineering

1 0