July 2005 - Boost - lists.preview.boost.org

Re: [boost] Library Proposal: Boost.Geom 2D and 3D GeometricPrimitives
by Hickerson, David A 02 Jul '05

02 Jul '05

I could not find the original message to look at the proposed code, is it on the web site some where? Here are my requirements for a Geometry library. 1. The primitives integrate with translational and rotational elements, such as homogenous transforms (4x4 matrices), quaterions, Euler angles, and translation vectors. 2. The translationals and rotation elements convert to one another where applicable. The rotational part of the homogenous transform convert to and from a rotational quaterion and to and from Euler angles, or quaterion to Euler angles. The translation parts can be extracted and set in the homogenous transform. 3. At a minimum, OpenGL array extraction from homogenous tranforms, points, and shapes. A float array in the order that OpenGL expects for these elements. Support for DirectX, and others would be good. I have done some of this in the library I wrote in 97. Dave -----Original Message----- From: Joel de Guzman [mailto:joel@boost-consulting.com] Sent: Tuesday, June 28, 2005 11:02 AM To: boost(a)lists.boost.org Subject: Re: [boost] Library Proposal: Boost.Geom 2D and 3D GeometricPrimitives Anis Benyelloul wrote: > Joel de Guzman <joel <at> boost-consulting.com> writes: > > >>How do you plan to implement your regions? If your Points can use >>native platform points, I assume your regions can also use native >>platform regions? Or are we talking about different things? I'm >>interested on how you can make it use the Macintosh classic Region, >>for example. > > > Well, let me think of it.... What is a region ? A collection of (non- > overlapping ?) boxes. Now what is a collection of boxes ? > - std::vector<box> > - boost::array<box, 20> > - box ; // Note: a single box ! > - XRegion ;// Maybe some pre-existing region object in other libraries > > As you see, the problem is quite the same: for one abstraction > (region) being > able to choose among many implementations, and just "plug" them in some > convenient wrapper class. > > Actually, I haven't studied much the subject, but it doesn't seem of > extrem > complexity ... Well, not so fast. Been there done that. The problem is how to interoperate on two regions. Example: I need to XOR a YRegion with a MacRegion. The thing is, a classic mac region is an opaque data type (actually, it's not implemented as a collection of boxes). The mere fact that it is opaque makes it impossible to even copy a mac region to a YRegion. Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

4 4

Re: [boost] Library Proposal: Boost.Geom 2D and3DGeometricPrimitives
by Hickerson, David A 02 Jul '05

02 Jul '05

I put it on the Boost sand box as vec.zip . The algorithms work and it ran on Windows using Borland C++ 4.5/5.0, MS C++ 6.0, and SGI Irix 6.2 with I think the 7.2 compiler. I added a readme.txt to it to explain a little bit about it and ran CppDoc against too, don't know how useful that was though. Dave -----Original Message----- From: Andy Little [mailto:andy@servocomm.freeserve.co.uk] Sent: Thursday, June 30, 2005 3:52 PM To: boost(a)lists.boost.org Subject: Re: [boost] Library Proposal: Boost.Geom 2D and3DGeometricPrimitives "Hickerson, David A" <david.a.hickerson(a)boeing.com> wrote >I will locate the library this evening and upload it. One this about it >was I developed it before I saw Boost and had developed my own >conventions. I did this as part of a thesis work in Robotics and will I >was working for a 3D Vis company. There are references to robot >convension and a graphics convension. This is because the robotics and >engineering use a column vector notation and the graphics community >uses a row vector convension or least OpenGL does. > > If those involved with Boost are interested, I would like to donate > the code for use in developing the capabilities here. I'd be keen to see it too. Andy Little _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

Re: [boost] [home page] Marketing?
by BRIDGES Dick 01 Jul '05

01 Jul '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] On > Behalf Of David Abrahams > Sent: Friday, July 01, 2005 11:29 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] [home page] Marketing? > > Peter Simons <simons(a)cryp.to> writes: > > > Martin Wille writes: > > > > > Sorry disappoint you, but, frankly, "So download" <insert > > > product here> "and start enjoying it" is exactly the kind > > > of text I _never_ want to read in anything supposed to > > > provide information. > > > > I wanted to say the say the exact same thing, Martin. I couldn't > > care less about having a link to "collected appeals to authority" > > on the front page. I use the Boost libraries for technical > > reasons, not because Bjarne Stroustrup (reportedly) uttered a > > fancy one-liner about them at one point. > > You don't think we'll draw new users because Scott Meyers has > recommended that people familiarize themselves with Boost? I think it might depend on the market and the particular segments the home page is attempting to gain. I'm just a programmer, but when I want to use Boost libraries, I have to sell the idea to certain groups and the home page helps. (I'll leave out the programmers we'd like to "convert".) I have to sell the Boost libraries to our legal department. Most of their experience involves the GNU GPL. Oh good. Good thing I have that License link. Even if the Acknowledgements at the bottom of the License page cannot be moved to the top and put it in 72 point type, Harvard Law still sells. I have to sell the Boost libraries to mid-level managers. It's been a while since they've fired up a compiler but they're pretty good with project management software. You [plural, no one and everyone] may not realize it, but the mailing list links and a quick tour through current threads screams "SUPPORT". Boost "people" are not only helpful, they are nice! That learning curve might not be too steep after all. I have to sell the Boost libraries to QA, version control, build-meister, etc. What about quality, standards and backward compatibility? The links to reviews take care of most of those questions. Charity work performed by some Boost members for a certain international organization doesn't go unnoticed either. Now if our own code were that good... ;) <point> I have to sell the Boost libraries to what I'll call "non-programming other management" (includes Sales and Marketing). They tend to be what I'll call "conservative": if they're not familiar with it, they tend to be suspicious. They created NIH. [My attitude may show here.] I don't need 50 million flies but a few dozen well-known examples would help to increase name recognition *a lot*. I have this dream that someday one of them asks: "Hey, can we tell *OUR* customers we use the Boost libraries?" </point> BTW: The only segment I've never had to sell Boost to are those that use their C++ compilers to compile C++. Just my $.02 As always, thanks to all for the code and the mentoring. Dick Bridges

1 0

Re: [boost] [serialization] Notes from a new boost user
by Michael Behrns-Miller 01 Jul '05

01 Jul '05

> David Abrahams wrote: >> "Michael Behrns-Miller" <m(a)thedigitalmachine.com> writes: >> >>> 2) The new "const required to save" restriction bit me, took a day or >>> two to work through the mailing list and #boost to figure out the >>> problem. Is >> >> Did it prevent a bug, or did it just cost you 2 days of your valuable >> time? > > Were you not tempted to just use "const_cast"? Why not? I temporarily tried it and got it to work, but that wasn't an acceptable solution to me. I hate casting, immediately makes me reassess the design. Which I did, which led me to the answer. :P I expected to have ramp-up time with boost. I probably spent a day fiddling with bjam, a half day figuring out to include boost libraries, and a day or two on the const issue. Not full days, just poking around in my spare time. I got everything working under vc71 and gcc 3.3.5 way before getting frustrated, so I was happy. Also, to be fair to you, I was using a verbatim copy of the demo code to start, which I believe needs updating. I was working from documentation that didn't cover the const issue. With those two improvements, I would have been better off. But I am not foolish enough to pretend I have the answer to the const issue, especially given there are many current serialization users. Just providing some feedback. <ducks and runs> > Whenever I do include a BOOST_STATIC_ASSERT that a library user might be > expected to trip on, I include comments at that point which describes the > problem and hopefully a helpful course of action. When I build in my > environment (VC 7.1) and double click on the error message, the > BOOST_STATIC_ASSERT pops up and right there is the comment explaining it. > To me, this seems pretty good and I would hope that this would minimize > the time a user has to spend looking for sources to these problems. In > fact, I have received mail from users that have remarked upon exactly > this feature/practice as being very helpful in understanding these other > wise very subtle errors. By far the best one is when one uses an > xml_archive to serialize something which doesn't have a variable name > attached. It pops a STATIC_ASSERT and the comment right there is the > comment describing what one is doing wrong. I agree, that's where I started when figuring it out, looking at the error line, which clued me in. Thanks again.

2 1

[serialization] Notes from a new boost user
by Michael Behrns-Miller 01 Jul '05

01 Jul '05

> I've become very skeptical of my ability to predict how other programmers > are going to address things. I'm willing to wait and see. > > So I'm anxious to see where this goes. If in fact we do get a wave of > users with problems, I'll be forced to modify my point of view in the > face of the facts. If (almost) no one complains (perhaps unlikely) then > there will be no issue. If there are a fair number of complaints - but > it turns out that a significant portion are due to real mistakes - we > might be in for another debate. But given more data, I would expect it > to be of a different character. If it turns out (almost) none of the > cases are real problems, then I'll have to accept as a fact that its a > bad idea. As a new boost user I thought I would humbly submit some feedback. Forgive me if I missed nuances of the existing debates. 1) I love the serialization library, I'm sure many of us have done similar code before, and it's great to see work towards a standardized solution. Really useful, thanks Robert! 2) The new "const required to save" restriction bit me, took a day or two to work through the mailing list and #boost to figure out the problem. Is there a way to make the end-of-the-chain error message (`boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value') more clear? I would rate the severity of the difficulty a 2 or 3 out of 10, from a new user's perspective. It seemed intuitive enough once I understood the requirement. Putting the serialization save calls within a const save(archive) function of the object being serialized made it a non-issue for me. I haven't used it enough to say I won't run into the const issue again, but at least I know about it now. 3) I realize I can split serialize() into separate load/save functions. However, I appreciate the recommendation to use one serialize() function, where the load/save order is easier to maintain. However again, I absolutely need (I think :>) to know, within that function, if I am loading or saving. It's the only way I can efficiently handle versioning or handle dynamic allocations, and still use one serialize() function, as far as I can tell. Bottom line: I now have isSaving(archive)/isLoading(archive) functions, can these be added to the library? Or am I approaching this wrong? As I've said, I'm brand new at this. I'm providing this feedback for two reasons: to give you an idea of what I ran into as a new user, and to get suggestions on anything I'm approaching in the wrong way. Thanks again boost.

3 4

[serialization] Notes from a new boost user
by Michael Behrns-Miller 01 Jul '05

01 Jul '05

> I've become very skeptical of my ability to predict how other programmers > are going to address things. I'm willing to wait and see. > > So I'm anxious to see where this goes. If in fact we do get a wave of > users with problems, I'll be forced to modify my point of view in the > face of the facts. If (almost) no one complains (perhaps unlikely) then > there will be no issue. If there are a fair number of complaints - but > it turns out that a significant portion are due to real mistakes - we > might be in for another debate. But given more data, I would expect it > to be of a different character. If it turns out (almost) none of the > cases are real problems, then I'll have to accept as a fact that its a > bad idea. As a new boost user I thought I would humbly submit some feedback. Forgive me if I missed nuances of the existing debates. 1) I love the serialization library, I'm sure many of us have done similar code before, and it's great to see work towards a standardized solution. Really useful, thanks Robert! 2) The new "const required to save" restriction bit me, took a day or two to work through the mailing list and #boost to figure out the problem. Is there a way to make the end-of-the-chain error message (`boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value') more clear? I would rate the severity of the difficulty a 2 or 3 out of 10, from a new user's perspective. It seemed intuitive enough once I understood the requirement. Putting the serialization save calls within a const save(archive) function of the object being serialized made it a non-issue for me. I haven't used it enough to say I won't run into the const issue again, but at least I know about it now. 3) I realize I can split serialize() into separate load/save functions. However, I appreciate the recommendation to use one serialize() function, where the load/save order is easier to maintain. However again, I absolutely need (I think :>) to know, within that function, if I am loading or saving. It's the only way I can efficiently handle versioning or handle dynamic allocations, and still use one serialize() function, as far as I can tell. Bottom line: I now have isSaving(archive)/isLoading(archive) functions, can these be added to the library? Or am I approaching this wrong? As I've said, I'm brand new at this. I'm providing this feedback for two reasons: to give you an idea of what I ran into as a new user, and to get suggestions on anything I'm approaching in the wrong way. Thanks again boost.

3 2

Boost.Build v2 with VC8
by Johan Johansson 01 Jul '05

01 Jul '05

How do you do it? I've tried adding using msvc : 8.0 to user.config and I've tried using msvc : vc-8_0 since that didn't appear to work. At that point I got the message that the python lib wouldn't be build - but I've set both PYTHON_ROOT and PYTHON_VERSION to the satisfaction of Boost.Build v1. Can someone please tell me what to configure and the exact command line I should use to build it? I've already spent 2 hours running in circles in the docs and that doesn't seem to get me anywhere. Thanks, Johan

2 1

[serialization] Regressions?
by Vladimir Prus 01 Jul '05

01 Jul '05

Hi Robert, I've just updated by Boost tree and run in a number of compile errors. One is pretty easy -- I've committed the attached trivial patch to split_member.hpp. Another is this: ....boost/boost/archive/detail/oserializer.hpp:551: error: incomplete type `boost::STATIC_ASSERTION_FAILURE<false>' does not have member `value' instantiated from this code of mine: ofstream ofs(av[2]); boost::archive::binary_oarchive oa(ofs); oa << *data_builder.finish(); Where 'finish' returns auto_ptr<Data>. It's looks like serialization checks if the serialized type is 'const' and if not, complains. Basically, it's some heuritic to prevent saving on-stack object (though I don't understand why it would work at al). I find this a bit too much . I have no reason whatsoever to make 'finish' return auto_ptr<const Data>. And writing oa << const_cast<const Data&>(*data_builder.finish()); looks very strange. And modifying all places where I get this error is not nice too. So, can this static assert be removed? Then, I get ambiguity in iserializer.hpp, in this code: #ifndef BOOST_NO_FUNCTION_TEMPLATE_ORDERING template<class Archive, class T> inline void load(Archive &ar, const serialization::nvp<T> &t){ load(ar, const_cast<serialization::nvp<T> &>(t)); } For some reason, both boost::archive::load and some other 'load' in 'boost' namespace (part of earlier serialization lib) that I still use are considered overload candidates. Adding explicit boost::archive:: fixes this. See attached patch. Then I get error at this code: ar << boost::lexical_cast<std::string>(*this); The error message is: error: no match for 'operator<<' in 'ar << boost::lexical_cast(Source) [with Target = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, Source = lvk::nm_model::BlockFormula]()' /space/NM/boost/boost/archive/detail/interface_oarchive.hpp:75: error: candidates are: Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(T&) [with T = std::basic_string<char, std::char_traits<char>, std::allocator<char> >, Archive = boost::archive::binary_oarchive] ...unrelated operator<< definitions snipped... Apparently, passing rvalue to "T&" does not work. Yes another attached patch fixes this issue. - Volodya

9 73

Boost regression notification (2005-07-01)
by Douglas Gregor 01 Jul '05

01 Jul '05

Boost regression test failures ------------------------------ Report time: 2005-07-01T15:12:34Z This report lists all regression test failures on release platforms. WARNING: The following libraries have failing regression tests but do not have a maintainer on file. Once a maintainer is found, add an entry to libs/maintainers.txt to eliminate this message. random preprocessor io Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 337 failures in 14 libraries: bind (1) io (2) iostreams (1) iterator (2) preprocessor (1) program_options (13) python (56) random (3) regex (2) serialization (239) spirit (5) test (6) thread (2) wave (4) |bind| mem_fn_eq_test: intel-win32-8_1 |io| ios_state_unit_test: intel-win32-8_1 intel-win32-8_1 |iostreams| counter_test: vc-8_0 |iterator| filter_iterator_test: intel-win32-8_1 lvalue_concept_fail: intel-win32-8_1 |preprocessor| seq: cw-8_3 |program_options| cmdline_test: vc-7_0 cmdline_test_dll: mingw-3_4_2 vc-7_0 parsers_test: vc-7_0 parsers_test_dll: vc-7_0 positional_options_test_dll: mingw-3_4_2 unicode_test: vc-7_0 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin vc-7_0 variable_map_test: vc-7_0 variable_map_test_dll: vc-7_0 vc-8_0 |python| andreas_beyer: intel-win32-8_1 args: intel-win32-8_1 auto_ptr: intel-win32-8_1 back_reference: intel-win32-8_1 ben_scott1: intel-win32-8_1 bienstman1: intel-win32-8_1 bienstman2: intel-win32-8_1 bienstman3: intel-win32-8_1 builtin_converters: intel-win32-8_1 callbacks: intel-win32-8_1 const_argument: intel-win32-8_1 crossmod_exception: intel-win32-8_1 data_members: intel-win32-8_1 defaults: intel-win32-8_1 dict: intel-win32-8_1 docstring: intel-win32-8_1 embedding: intel-win32-8_1 enum: intel-win32-8_1 exception_translator: intel-win32-8_1 extract: gcc-3.3.6-linux intel-win32-8_1 implicit: intel-win32-8_1 injected: intel-win32-8_1 iterator: intel-win32-8_1 keywords: intel-win32-8_1 list: gcc-3.3.6-linux intel-win32-8_1 long: intel-win32-8_1 map_indexing_suite: intel-win32-8_1 minimal: intel-win32-8_1 multi_arg_constructor: intel-win32-8_1 nested: intel-win32-8_1 object: intel-win32-8_1 opaque: intel-win32-8_1 operators: gcc-3.3.6-linux intel-win32-8_1 pearu1: intel-win32-8_1 pickle1: intel-win32-8_1 pickle2: intel-win32-8_1 pickle3: intel-win32-8_1 pickle4: intel-win32-8_1 polymorphism: intel-win32-8_1 polymorphism2: intel-win32-8_1 properties: intel-win32-8_1 raw_ctor: intel-win32-8_1 return_arg: intel-win32-8_1 shared_ptr: intel-win32-8_1 slice: gcc-3.3.6-linux intel-win32-8_1 staticmethod: intel-win32-8_1 str: intel-win32-8_1 test_pointer_adoption: intel-win32-8_1 try: intel-win32-8_1 tuple: intel-win32-8_1 vector_indexing_suite: intel-win32-8_1 virtual_functions: intel-win32-8_1 |random| random_test: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 |regex| regex_regress: intel-win32-8_1 regex_regress_dll: intel-win32-8_1 |serialization| test_array_text_archive_dll: cw-9_5-darwin test_array_text_warchive_dll: cw-9_5-darwin test_array_xml_archive_dll: cw-9_5-darwin test_array_xml_warchive_dll: cw-9_5-darwin test_binary_text_archive_dll: cw-9_5-darwin test_binary_text_warchive_dll: cw-9_5-darwin test_binary_xml_archive_dll: cw-9_5-darwin test_binary_xml_warchive_dll: cw-9_5-darwin test_class_info_load_binary_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_binary_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_archive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_text_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux vc-6_5 test_class_info_load_xml_archive: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_archive_dll: gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_load_xml_warchive_dll: cw-9_5-darwin gcc-3.3.6-linux gcc-3.4.4-linux test_class_info_save_text_archive_dll: cw-9_5-darwin test_class_info_save_text_warchive_dll: cw-9_5-darwin test_class_info_save_xml_warchive_dll: cw-9_5-darwin test_const_load_fail1: borland-5_6_4 test_const_load_fail1_nvp: borland-5_6_4 test_const_load_fail2: borland-5_6_4 test_const_load_fail2_nvp: borland-5_6_4 test_const_save_fail1: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail2: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_const_save_fail3: msvc vc-6_5 vc-6_5-stlport vc-7_0 test_contained_class_text_archive_dll: cw-9_5-darwin test_contained_class_text_warchive_dll: cw-9_5-darwin test_contained_class_xml_archive_dll: cw-9_5-darwin test_contained_class_xml_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin test_delete_pointer_text_archive_dll: cw-9_5-darwin test_delete_pointer_text_warchive_dll: cw-9_5-darwin test_delete_pointer_xml_archive_dll: cw-9_5-darwin test_delete_pointer_xml_warchive_dll: cw-9_5-darwin test_demo: intel-win32-8_1 test_demo_auto_ptr_dll: cw-9_5-darwin test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception: intel-win32-8_1 test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc-6_5 test_demo_pimpl_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_polymorphic_dll: cw-9_5-darwin test_demo_portable_archive: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 vc-7_0 vc-7_1 vc-8_0 test_demo_portable_archive_dll: intel-win32-8_1 intel-win32-8_1 intel-win32-8_1 test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 vc-7_0 test_demo_xml_load: intel-win32-8_1 test_demo_xml_save: intel-win32-8_1 test_deque_text_archive_dll: cw-9_5-darwin test_deque_text_warchive_dll: cw-9_5-darwin test_deque_xml_archive_dll: cw-9_5-darwin test_deque_xml_warchive_dll: cw-9_5-darwin test_derived_class_ptr_text_archive_dll: cw-9_5-darwin test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin test_derived_class_text_archive_dll: cw-9_5-darwin test_derived_class_text_warchive_dll: cw-9_5-darwin test_derived_class_xml_archive_dll: cw-9_5-darwin test_derived_class_xml_warchive_dll: cw-9_5-darwin test_derived_text_archive_dll: cw-9_5-darwin test_derived_text_warchive_dll: cw-9_5-darwin test_derived_xml_archive: vc-8_0 test_derived_xml_warchive_dll: cw-9_5-darwin test_diamond_binary_archive: cw-8_3 cw-9_5-darwin test_diamond_binary_archive_dll: cw-9_5-darwin test_diamond_text_archive: cw-8_3 cw-9_5-darwin test_diamond_text_archive_dll: cw-9_5-darwin test_diamond_text_warchive: cw-8_3 cw-9_5-darwin test_diamond_text_warchive_dll: cw-9_5-darwin test_diamond_xml_archive: cw-8_3 cw-9_5-darwin test_diamond_xml_archive_dll: cw-9_5-darwin test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin test_diamond_xml_warchive_dll: cw-9_5-darwin test_list_ptrs_text_archive_dll: cw-9_5-darwin test_list_ptrs_text_warchive_dll: cw-9_5-darwin test_list_ptrs_xml_archive_dll: cw-9_5-darwin test_list_ptrs_xml_warchive_dll: cw-9_5-darwin test_list_text_archive_dll: cw-9_5-darwin vc-8_0 test_list_text_warchive_dll: cw-9_5-darwin test_list_xml_archive_dll: cw-9_5-darwin test_list_xml_warchive_dll: cw-9_5-darwin test_map_binary_archive_dll: msvc vc-6_5 vc-7_0 test_map_text_archive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_text_warchive_dll: cw-9_5-darwin msvc vc-6_5 vc-7_0 test_map_xml_archive_dll: cw-9_5-darwin test_map_xml_warchive_dll: cw-9_5-darwin test_mi_text_warchive_dll: intel-win32-8_1 test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin msvc vc-6_5 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin test_no_rtti_text_archive_dll: intel-win32-8_1 test_non_default_ctor_text_archive_dll: cw-9_5-darwin test_non_default_ctor_text_warchive_dll: cw-9_5-darwin test_non_default_ctor_xml_archive_dll: cw-9_5-darwin test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin test_non_intrusive_text_archive_dll: cw-9_5-darwin test_non_intrusive_text_warchive_dll: cw-9_5-darwin test_non_intrusive_xml_archive_dll: cw-9_5-darwin test_non_intrusive_xml_warchive_dll: cw-9_5-darwin test_null_ptr_text_archive_dll: cw-9_5-darwin test_null_ptr_text_warchive_dll: cw-9_5-darwin test_null_ptr_xml_warchive_dll: cw-9_5-darwin test_nvp_text_archive_dll: cw-9_5-darwin test_nvp_text_warchive_dll: cw-9_5-darwin test_nvp_xml_archive_dll: cw-9_5-darwin test_nvp_xml_warchive_dll: cw-9_5-darwin test_object_text_warchive_dll: cw-9_5-darwin test_object_xml_warchive_dll: cw-9_5-darwin test_optional_text_archive_dll: cw-9_5-darwin test_optional_text_warchive_dll: cw-9_5-darwin test_optional_xml_archive_dll: cw-9_5-darwin test_optional_xml_warchive_dll: cw-9_5-darwin test_polymorphic_text_archive_dll: cw-9_5-darwin test_polymorphic_text_warchive_dll: cw-9_5-darwin test_polymorphic_xml_archive_dll: cw-9_5-darwin test_polymorphic_xml_warchive_dll: cw-9_5-darwin test_primitive_text_warchive_dll: cw-9_5-darwin test_primitive_xml_warchive_dll: cw-9_5-darwin test_private_ctor_dll: cw-9_5-darwin test_recursion_text_archive_dll: cw-9_5-darwin test_recursion_text_warchive_dll: cw-9_5-darwin test_recursion_xml_archive_dll: cw-9_5-darwin test_recursion_xml_warchive_dll: cw-9_5-darwin test_reset_object_address_dll: cw-9_5-darwin test_set_text_archive_dll: cw-9_5-darwin test_set_text_warchive_dll: cw-9_5-darwin test_set_xml_archive_dll: cw-9_5-darwin test_set_xml_warchive_dll: cw-9_5-darwin test_shared_ptr_132_binary_archive: borland-5_6_4 test_shared_ptr_132_binary_archive_dll: borland-5_6_4 vc-8_0 test_shared_ptr_132_text_archive: borland-5_6_4 test_shared_ptr_132_text_archive_dll: borland-5_6_4 test_shared_ptr_132_text_warchive: borland-5_6_4 test_shared_ptr_132_text_warchive_dll: borland-5_6_4 test_shared_ptr_132_xml_archive: borland-5_6_4 test_shared_ptr_132_xml_archive_dll: borland-5_6_4 test_shared_ptr_132_xml_warchive: borland-5_6_4 test_shared_ptr_132_xml_warchive_dll: borland-5_6_4 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin test_simple_class_text_archive_dll: cw-9_5-darwin test_simple_class_text_warchive_dll: cw-9_5-darwin test_simple_class_xml_archive_dll: cw-9_5-darwin test_simple_class_xml_warchive_dll: cw-9_5-darwin test_split_text_archive_dll: cw-9_5-darwin test_split_text_warchive_dll: cw-9_5-darwin test_split_xml_warchive_dll: cw-9_5-darwin test_tracking_text_archive_dll: cw-9_5-darwin test_tracking_text_warchive_dll: cw-9_5-darwin test_tracking_xml_warchive_dll: cw-9_5-darwin test_variant_text_archive_dll: cw-9_5-darwin test_variant_text_warchive_dll: cw-9_5-darwin test_variant_xml_archive_dll: cw-9_5-darwin test_variant_xml_warchive_dll: cw-9_5-darwin test_vector_text_archive_dll: cw-9_5-darwin test_vector_text_warchive_dll: cw-9_5-darwin test_vector_xml_archive_dll: cw-9_5-darwin test_vector_xml_warchive_dll: cw-9_5-darwin |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin numerics_tests: gcc-3.2.3-linux numerics_tests_debug: gcc-3.2.3-linux owi_mt_tests: gcc-3_3-darwin |test| errors_handling_test: cw-9_5-darwin vc-8_0 test_fp_comparisons: borland-5_6_4 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin |thread| test_mutex: gcc-2.95.3-stlport-4.6.2-linux test_read_write_mutex: borland-5_6_4 |wave| testwave: cw-8_3 cw-9_5-darwin gcc-3.2.3-linux gcc-3.3.6-linux

1 0

Going temporarily offline.
by Hubert Holin 01 Jul '05

01 Jul '05

Somewhere in the E.U., le 01/07/2005 Bonjour As of tonight and for about a month (Hurray!!!) I will be on vacation, and for the most part totally offline. So as not to possibly delay the 1.33 release, I state here clearly that anybody is welcome to check-in any (useful) change to the libraries I maintain (Quaternions, Octonions & Special Functions). As far as these libraries stand today, for the platforms that are taken into account for the release, no outstanding problem seem to remain (either the platform passes or is marked as an expected failure). There remains a vexing point with respect to some platforms (notably 64 bits platforms) where the libraries fail because of "long double" issues. I believe these are due to a bug (or severe QOI problem) in libstdc++, but unfortunately so far no progress seems to have been made to solve the problem if indeed libstdc++ is the culprit, and I am loath to mark these platforms as expected failures (heck, one of them I my development system!). I propose we leave these as they stand now, and re-investigate after the release. Merci et bonnes vacances! Hubert Holin

1 0