- Boost - lists.preview.boost.org

[parameter] missing docs?
by Joaquín Mª López Muñoz 09 Jun '05

09 Jun '05

Are the docs for Boost.Parameter already into the CVS? I cannot seem to find them. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[filesystem] error codes revisited
by Beman Dawes 09 Jun '05

09 Jun '05

Peter Dimov suggested that Boost.Filesystem's error reporting codes use the POSIX <cerrno>/<errno.h> codes as the portable way to encode errors. That made a lot of sense for POSIX systems, and since POSIX is now an ISO standard (ISO/IEC 9945:2002), other portions of Boost.Filesystem are also as of the i18n branch being formally defined by reference to the ISO POSIX standard. Checking how the various standards interrelate as far as errno.h, cerrno, and errno definitions are concerned, the C++ and POSIX standards both defer to the C standard, although POSIX does add additional codes. No problems there. As far as actual header implementations go, there was a concern that the Windows errno.h implementations didn't provide the needed definitions (since C only mandates EDOM, EILSEQ, and ERANGE). That turned out to be a non-problem. The Windows implementations only provide a subset of the POSIX macros, but with few exceptions they do provide all the macros Boost.Filesystem users will need. One exception was that Borland fails to define one of the needed macros. There were also two cases where additional non-POSIX macros were needed, but the standards do permit extensions, so again no problem. That has been worked around by providing a <boost/filesystem/cerrno.hpp> header which sucks in <cerrno> and adds any needed definitions. I had some concerns about Boost.Filesystem headers gratuitously including <cerrno> (or <boost/filesystem/cerrno.hpp>) because that could cause macro name clashes. But it turned out the Boost.Filesystem headers have no reason to include <cerrno> or <boost/filesystem/cerrno.hpp>. So no problem. The CVS filesystem i18n branch now has the POSIX aligned error mechanisms in place. Seems to work well and be a very nice improvement to the library. Thanks to Peter for the suggestion! --Beman

1 0

[boost][date_time] errors in time_facet.hpp (cvs HEAD)
by Jan Hermelink 09 Jun '05

09 Jun '05

I think there are several errors in time_facet.hpp from cvs HEAD: The lines using std::basic_string::find() evaluate the return code wrongly, e.g. line 227: if (format.find(seconds_with_fractional_seconds_format)) { should be if (format.find(seconds_with_fractional_seconds_format) != string_type::npos) { I think. In addition I think "%%" should always evaluate to "%" and leave the following char unexpanded. Current e.g. "%%s" evaluates to "%59.000000", not to "%s". This is the outcome of using boost::algorithm::replace_all(). Otherwise thank you for your great library! Jan

2 1

Serialization - no & operator for primitives
by Marcin Tustin 09 Jun '05

09 Jun '05

I'm using a recent (a few days old) cvs version of boost, and the serialization libraries, and Visual Studio 7.1 is producing the error below. This is only happening to classes which I am exporting (like BOOST_CLASS_EXPORT_GUID(D2::Message,"D2::Message");). The reason I am exporting them is that they are in many cases a) subclasses of each other b) accessed through a pointer. Any help would be deeply appreciated. My code is: template<class Archive > static void serialize(Archive & ar, D2::Message& g, const unsigned int version) { ar & g.getType(); // an int - error complains about this line. ar & g.getSender(); // a string ar & g.getMessage(); // a string } Error message: c:\D2\API\NewClient\EnhancedMessageHandler.h(132) : error C2679: binary '&' : no operator found which takes a right-hand operand of type 'uint32' (or there is no acceptable conversion) C:\boost\boost-cvs-20050606\boost\boost\serialization\serialization.hpp( 140) : see reference to function template instantiation 'void boost::serialization::serialize<Archive>(Archive &,D2::Message &,const unsigned int)' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,IplJrsMediaTimePoint>::tail,IplJrsMediaTimePoint>: :head ] C:\boost\boost-cvs-20050606\boost\boost\archive\detail\iserializer.hpp(1 61) : see reference to function template instantiation 'void boost::serialization::serialize_adl<Archive,T>(Archive &,T &,const unsigned int)' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,IplJrsMediaTimePoint>::tail,IplJrsMediaTimePoint>: :head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\extended_type_info _typeid.hpp(71) : while compiling class-template member function 'void boost::archive::detail::iserializer<Archive,T>::load_object_data(boost:: archive::detail::basic_iarchive &,void *,const unsigned int) const' with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\archive\detail\iserializer.hpp(1 72) : see reference to class template instantiation 'boost::archive::detail::iserializer<Archive,T>' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\archive\detail\iserializer.hpp(1 71) : while compiling class-template member function 'const boost::archive::detail::basic_iserializer &boost::archive::detail::pointer_iserializer<T,Archive>::get_basic_seria lizer(void) const' with [ T=D2::Message, Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head ] C:\boost\boost-cvs-20050606\boost\boost\archive\detail\iserializer.hpp(5 01) : see reference to class template instantiation 'boost::archive::detail::pointer_iserializer<T,Archive>' being compiled with [ T=D2::Message, Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(78) : see reference to function template instantiation 'const boost::archive::detail::basic_pointer_iserializer &boost::archive::detail::instantiate_pointer_iserializer<Archive,T>(Arch ive *,T *)' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(74) : while compiling class-template member function 'void boost::archive::detail::export_impl::archive<Archive,T>::i::invoke(void) ' with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(105) : see reference to class template instantiation 'boost::archive::detail::export_impl::archive<Archive,T>::i' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(89) : while compiling class-template member function 'void boost::archive::detail::export_impl::archive<Archive,T>::instantiate(voi d)' with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(116) : see reference to class template instantiation 'boost::archive::detail::export_impl::archive<Archive,T>' being compiled with [ Archive=boost::archive::detail::export_impl::for_each_archive<boost::arc hive::detail::export_impl::for_each_archive<boost::archive::detail::know n_archive_types::type,D2::Message>::tail,D2::Message>::head, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(115) : while compiling class-template member function 'void boost::archive::detail::export_impl::for_each_archive<ASeq,T>::instantia te(void)' with [ ASeq=boost::archive::detail::export_impl::for_each_archive<boost::archiv e::detail::known_archive_types::type,D2::Message>::tail, T=D2::Message ] C:\boost\boost-cvs-20050606\boost\boost\serialization\export.hpp(122) : see reference to class template instantiation 'boost::archive::detail::export_impl::for_each_archive<ASeq,T>' being compiled with [ ASeq=boost::archive::detail::export_impl::for_each_archive<boost::archiv e::detail::known_archive_types::type,D2::Message>::tail, T=D2::Message ] Marcin Tustin IT Innovation Centre 2 Venture Road Chilworth Science Park Southampton, SO16 7NP, UK tel: +44 23 8076 0834 fax: +44 23 8076 0833 mailto:mt@it-innovation.soton.ac.uk http://www.it-innovation.soton.ac.uk

2 1

[testing] [math] [gcc] Problems with long double math functions
by Caleb Epstein 09 Jun '05

09 Jun '05

These test failures all seem to stem from problems with std::exp (long double) and perhaps some other math functions using long double on gcc. Does this smell like a gcc bug, or is there something wrong with the tests? gcc-4_0-darwin: http://tinyurl.com/8tts6 http://tinyurl.com/atzbx gcc-windows: http://tinyurl.com/dwmdk http://tinyurl.com/9to33 gcc-3_4_3-sunos: http://tinyurl.com/8zvpz http://tinyurl.com/bx6mt -- Caleb Epstein caleb dot epstein at gmail dot com

2 1

[program_options, type_traits] is_reference and VC 7.0
by Vladimir Prus 09 Jun '05

09 Jun '05

Hi, I get program_options failures on VC 7.0 that result from the following sequences of events: variable_map::as<string> is called any_cast<string&> is called the following code in any.hpp gives static assertion: typedef BOOST_DEDUCED_TYPENAME remove_reference<ValueType>::type nonref; #ifdef BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION // If 'nonref' is still reference type, it means the user has not // specialized 'remove_reference'. // Please use BOOST_BROKEN_COMPILER_TYPE_TRAITS_SPECIALIZATION macro // to generate specialization of remove_reference for your class // See type traits library documentation for details BOOST_STATIC_ASSERT(!is_reference<nonref>::value); The problem is that on VC 7.0 specializations for remove_reference must be defined explicitly, and it's not done for string and wstring. I see three choices: 1. Declare specialization for string and wstring in program_options 2. Declare them somewhere in type_traits 3. Mark 7.0 as unsupported. 4. Don't use any_cast to reference type I don't like (4) because I've introduced cast to reference myself explicitly for program_options sake. (1) can lead to conflicts with user code. So it leaves (2) and (3). Any opinions which one is better? - Volodya

5 11

[Ann]: Dox - a C++ documentation tool
by Narech Koumar 08 Jun '05

08 Jun '05

Dear all, A beta test of a C++ documentation tool, Dox, is transpiring at: http://dox.isfotek.se Constructive feedback and angry comments are greatly appreciated. Thanks, - Narech Koumar

1 0

Fwd: [serialization] test_demo_portable_archive failures
by Caleb Epstein 08 Jun '05

08 Jun '05

Sorry, these should have been CC'ed to this list earlier (two messages inline below): ---------- Forwarded message ---------- From: Caleb Epstein <caleb.epstein(a)gmail.com> Date: Jun 8, 2005 5:48 PM Subject: [serialization] test_demo_portable_archive failures To: Running Boost regression tests <boost-testing(a)lists.boost.org>, Beman Dawes <bdawes(a)acm.org> The sole remaining failures for gcc-3_4_3-sunos appear to be the test_demo_portable_archive{,_dll} tests in the serialization library. These tests are failing because the numeric data that is written to the archive is two \x00 bytes for each value, which causes the restored object to contain all zeroes instead of the correct random data, and the comparison operation fails. My first thought was that this was an endian-ness problem, and in the end I was right. There is a block of code in portable_binary_[io]archive.hpp that checks #ifdef BOOST_BIG_ENDIAN. For some reason this macro is *not* being defined for me on SunOS. I can't find anywhere in Boost that it actually *is* defined, except <boost/detail/limits.hpp>, but this header is not included and trying to include it explicitly yields a slew of compiler errors. So I rebuilt the test program, adding -DBOOST_BIG_ENDIAN to the compiler command line. I still get the identical failure and the same \x00 bytes written to the archive. Looking more closely at the code that is doing the byte-swapping, there are three bugs: portable_binary_oarchive::save_impl: * last is initialized to first + size - 1. This should be first + sizeof (l) - 1; * the temporary variable x should be initialized with *last not *first portable_binary_iarchive::load_impl: * the temporary variable x should be initialized with *last not *first I've commited fixes for these to CVS just now, but I'm *not* sure how to best address the BOOST_BIG_ENDIAN issue. Any suggestions there? -- Caleb Epstein caleb dot epstein at gmail dot com ---------- Forwarded message ---------- On 6/8/05, Caleb Epstein <caleb.epstein(a)gmail.com> wrote: > I've commited fixes for these to CVS just now, but I'm *not* sure how > to best address the BOOST_BIG_ENDIAN issue. Any suggestions there? I think perhaps a new header file, <boost/endian.hpp> makes the most sense here. I don't think the definition of BOOST_BIG_ENDIAN / BOOST_LITTLE_ENDIAN belong in <boost/detail/limits.hpp> This header is not included unless BOOST_NO_LIMITS is defined, which I assume is only for non-standards-conforming implementations. -- Caleb Epstein caleb dot epstein at gmail dot com

1 0

RealNetworks has one more comment on boost.tokenizer
by Sebastien Martel 08 Jun '05

08 Jun '05

Hello boosters, Thank you for looking over the comments I posted. I completely forgot to mention one important thing boost.tokenizer 1.32 introduced that broke us when we moved from boost 1.31 : Here is my post on the matter on boost-users http://tinyurl.com/bc4av Essentially, the assign optimization (nice gains, thank you) adds requirements on the container type. We have a custom string classes that does not support it, but has a += member. So any use of tokenizer on these fails to compile. I sadly had to revert back to 1.31 behavior until this gets resolved. Thanks, -seb ( please cc me when replying, I do not follow boost@list ) -- Best regards, Sebastien mailto:smartel@real.com

2 2

[date_time] fractional_seconds: documentation suggestions
by Caleb Epstein 08 Jun '05

08 Jun '05

I think the specification of "fractional_seconds" in the time_duration class is unclear. Using the multi-argument constructor, and passing 1000 for the 4th argument, am I specifying milliseconds? Microseconds? Does it depend on the compile-time resolution of the class? If so (which is my suspicion), then using the 4-argument form of the ctor can lead to incorrect results if the resolution is changed. That seems like a bad thing. Looking at the implementation, I can see that I can divide the result of fractional_seconds() by the return value of ticks_per_second() to get a floating point value < 1.0, but I think that this should be more clearly spelled out in the section: doc/html/date_time/posix_time.html#date_time.posix_time.time_duration I'm not sure of the wording, but something like: *Construction* Mention that fractional_seconds depends on the compile-time resolution of the time_duration. I'd personally suggest it not be used and that the count-based construction be used instead. *Accessors Section* <tr> <td>static long ticks_per_second()</td> <td>The number of ticks per second. This is the resolution of the time_duration class</td> <td>long ticks_per_sec = time_duration::ticks_per_second();</td> <tr> <td>long fractional_seconds() const</td> <td>Get the number of fractional seconds. The return value will be in the range [0, ticks_per_second())</td> <td> time_duration td(1,2,3, 1000); td.fractional_seconds() --> 1000 <br/> double subsec = td.fractional_seconds() / time_duration::ticks_per_second () --> 0.001 (?) </td> Is this reasonable? -- Caleb Epstein caleb dot epstein at gmail dot com

2 1

Mailing list outage
by David Abrahams 08 Jun '05

08 Jun '05

-- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

RE: [boost] Re: Longer review period
by Brian Braatz 08 Jun '05

08 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Edward Diener > > I know I have never given a review but I feel that a 20 day period for > reviews rather than a 10 day period for reviews would give potential > reviewers, like me, a more comfortable zone in which to seriously look > at potential Boost software and give one. I think that would be a good > compromise between the present 10 day period, which seems to quick and a > full month period which seems too long. > > _______________________________________________ [Brian Braatz Writes:] Very much agree. The longer time will allow for some of us to FIND the time to participate. Additionally- I would like to suggest that if the period is extended, that the review manager periodically remind people of how much time is left. (if the discussion happens to die down) (i.e. every Monday morning or what not)

1 0

RealNetworks is using boost
by Sebastien Martel 08 Jun '05

08 Jun '05

Hello boosters, Name of the product: Rhapsody Name of the company: Real Networks Description of the Application and the Service: The Rhapsody Music Service allows its subscribers to legally download/transfer/burn over a million songs. The Rhapsody client software was built with many Boost libraries. URL of company and service: http://www.real.com/ Boost libraries used used with comments: boost.format Boost.Format is top notch. Using it is a bliss. boost.lexical_cast Quite useful. However pedantic use of streams to execute the conversions of basic types to/from strings is terrible. Had to be careful not to use in performance sensitive areas. I really wished there were a way to achieve performance comparable to c-runtime functions for ato* and *toa. boost.functional boost.function boost.bind These three libraries, along with smart pointer are the most used in our application. I could not imagine not having them handy. boost.smart_ptr Hands down, the most useful, and used library of the lot! boost.filesystem Not so happy here. This library looks promising, but there are a sum of little issues that makes me wonder if I should avoid using it in the future. 1- There is a bug on win98 when iterating a root drive. I sent a mail [http://lists.boost.org/MailArchives/boost-users/msg10391.php] about the problem on boost-users with a fix and never received a response. I might get better results by rephrasing the mail. 2- short-hand to build native paths using operator "/" is broken if you don't set the default name check to boost::filesystem::native. 3- What we really need is the reverse of the default library mode : have the library always work with native name-check and at the programmer's control, switch it to portable paths. There are WAY too many cases where we want to only work in native mode and portable path is the exception. 4- Lack of wstring/unicode support will become a problem very soon. 6- as noted in the do-list : "Windows: Some files seem to be poisoned to the point where you can't even do is_directory() on them without an access error. For example, pagefile.sys. Should directory_iterator ignore these files?" This is really a problem. A user must be very careful for exceptions when using iterators. They will throw. Overall this library, in it's current state, isn't a good fit for us. boost.date_time Simple to use, effective, does the job. I love the flexible input string parsing facilities, and the human readable ISO output. I created utilities to tie in with boost.filesystem so I can perform date_time calculations on files. Also had to create a layer to interface nicely with native locale date/time conversions api. I am sure every users of date_time that had to build UI apps ended up writing similar facilities. boost.tokenizer I glad to use tokenizer when we had to parse a whole bunch of weirdly formatted strings. It is a little bit tricky to get used to, especially the fact that tokenizer acquires references to its input in some cases instead of making a local copy. IMO, boost.Tokenizer would benefit from a policy design to fix this issue. I would prefer Tokenizer making a true copy of its input by default. boost.iterators Wow. Moving legacy iterating interfaces, or interfaces that should of been properly designed as iterators to STL compliant iterators was easy and painless. The gains in functionality to our code made by this library are invaluable. boost.array boost.optional Originally considered to implement an interface to value access of an embedded database but was discarded because of the _horrible_ compile times that appeared when introduced. Also considered for its visitation facility as a means to transport complex data to be rendered in UI controls. Again, dropped because of the compile times. boost.regex When you need it, it works magic. boost.thread Used to implement the monitor pattern in key areas. The 2 most desired features : static linking of boost.threads and ability to kill a thread. boost.preprocessor Used to implement repetitive unit-test code generation. The codebase benefited greatly from the clarity boost.preprocessor brought. -- Best regards, Sebastien mailto:smartel@real.com

3 3

Cache
by Maksym Motornyy 08 Jun '05

08 Jun '05

Hi all, I found that last discussion about cache classes in Boost was in year 2002. What happend at the end? Do we have cache in Boost or not? Sincerely, Maksym.

1 0

RE: [boost] Re: Re: Typeof: Review result
by Brian Braatz 08 Jun '05

08 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jonathan Turkanis > I'm one of those people who feels I must put a lot of work into a review. > For > the FSM review I broke this policy and wrote a review even though I had > only > studied the documentation. My review was negative; it was basically a list > of > what I considered to be shortcomings of the library. > > I ended up getting into an unpleasant exchange with the library author, > who > repeatedly challenged me to suggest concrete changes to the design to fix > the > perceived problems. I had examined the library more thoroughly, my guess > is that > I would have been able to suggest improvements. I don't blame the library > author > in this case; it's only natural to ask for an alternate design when you > are told > that your design is flawed; however, I simply didn't have sufficient time > to > devote to the library. [Brian Braatz Writes:] What are the expectations here? I find myself in this spot frequently. I see something up for review, and it ALWAYS happens at the worst time for me. I look at it, but I tend to not say much unless I can REALLY devote the time needed to give the library the proper amount of review time. There might be "no answer" to the expectations questions. But I would be curious how others feel about this. I.e. If I only have an hour or two to look at something- is it still useful for me to submit a review? Part of the problem I have is an enormous respect for what a boost library is. It is not something one slaps together just to get their name in lights (to me at least). A boost library makes you go "Wow". if it doesn't make you go "Wow" it doesn't belong in boost. But if I cannot devote the time needed to review something DEEPLY, I feel it is somewhat disrespectful for me to participate. Do you guys think I am wrong to feel this way? Or do you find the opinions of a quick review valuable? Brian

5 6

Internationalization
by Maksym Motornyy 08 Jun '05

08 Jun '05

Hello all, Is there any i18n library available (pending) in Boost? Sincerely, Maksym.

3 4

STLport builds
by Valentin Samko 08 Jun '05

08 Jun '05

I've been trying to build Boost.Thread and a number of other libraries for use in the software in the company where I work, and was only stopped by a number of STLport related problems. We already use header-only boost libraries for many years, and now would like to start using other boost libs. The main problems are: 1. We use unchecked STLport variant (i.e. without __STL_DEBUG). Unfortunately, Boost is not compatible with this mode, although a fix to add this mode is only a few lines of code in boost build. When I added this mode and recompiled boost, everything ran without any noticeable problems. I think it is worth adding this mode to boost build so that developers wouldn't have to patch boost build to add this mode. 2. It is very usefull that compiled boost libraries embed version number and different compile time options in their names. Unfortunately, STLport version is not embedded in their names (only 'p'). This creates a problem where two executables compiled against different STLport versions try to use the same Boost.WhateverLibrary dll. Are there any reasons not to embed STLport version number into boost library names? 3. A separate issue with Boost.Threads, where _sntprintf is called in boost_error in read_write_mutex.cpp, even when building with STLport, which does not have _snprintf. Also, there is bug in boost_error, which wrongly assumes that _sntprintf zero terminates the resulting string. I also wrote a patch to fix this problem. Is there any way to merge it into Boost.Thread? I understand that we could solve these problems either by not using STLport, or by changing the way we use it, but unfortunately, this is next to impossible for us, as we have a large software suite which is built and supported this way for years. Also, I think other developers would benefit if Boost provided workarounds/solutions for these common STLport problems. -- Valentin Samko http://val.samko.info

3 3

RE: [boost] Re: Kinook is using boost
by Brian Braatz 08 Jun '05

08 Jun '05

HAHAHAh When I clicked on the link earlier I was thinking the same thing. >From what I could gather on their web page- this is a commercial app that is closed source. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Robert Ramey > Sent: Tuesday, June 07, 2005 6:46 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Kinook is using boost > > Hmmm - any chance it could build the boost libraries and run the tests? > > Robert Ramey > > Kyle Alons wrote: > > Kinook Software (http://www.kinook.com) uses Boost in the following > > products: > > > > Product: Visual Build Professional > > Description: Visual Build Pro is a tool that enables developers, > > software process engineers, and build specialists to create an > > automated, repeatable process for building their software. Visual > > Build provides built-in support for Microsoft Visual Studio .NET and > > 2005, Visual Basic, Visual C++, Visual J++, SourceSafe, eMbedded > > Tools, Borland Delphi, JBuilder, C++Builder, and more. > > Parts of Boost used: any, mem_fn, regex, shared_ptr, smart_ptr, > > static_assert > > Web site: http://www.visualbuild.com/ > > > > Product: Ultra Recall > > Description: Ultra Recall is a personal information management (PIM) / > > knowledge management (KM) application for Microsoft Windows. It helps > > you capture, organize, and recall all of your electronic information > > across all the applications that you use. > > Parts of Boost used: format, shared_ptr, static_assert > > Web site: http://www.ultrarecall.com/ > > > > Thanks. > > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Kinook is using boost
by Kyle Alons 08 Jun '05

08 Jun '05

Kinook Software (http://www.kinook.com) uses Boost in the following products: Product: Visual Build Professional Description: Visual Build Pro is a tool that enables developers, software process engineers, and build specialists to create an automated, repeatable process for building their software. Visual Build provides built-in support for Microsoft Visual Studio .NET and 2005, Visual Basic, Visual C++, Visual J++, SourceSafe, eMbedded Tools, Borland Delphi, JBuilder, C++Builder, and more. Parts of Boost used: any, mem_fn, regex, shared_ptr, smart_ptr, static_assert Web site: http://www.visualbuild.com/ Product: Ultra Recall Description: Ultra Recall is a personal information management (PIM) / knowledge management (KM) application for Microsoft Windows. It helps you capture, organize, and recall all of your electronic information across all the applications that you use. Parts of Boost used: format, shared_ptr, static_assert Web site: http://www.ultrarecall.com/ Thanks. -- Kyle Alons Kinook Software, Inc. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jody Hagins > Sent: Tuesday, June 07, 2005 8:49 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: [function types] Formal Review begins today. > > > > Seems like we have a fundamentally different taste when it comes to > > documentation... [Jody Hagins Writes:] > > Probably. > [Brian Braatz Writes:] Allow me to suggest 2 ways of thinking about library documentation: 1- The better the documentation is, and the more it speaks to the average user, the more usage the library will have. If the docs don't make sense, people will SKIP using the lib. (which is a shame) 2- The lower the skills required of the reader the better. I realize one can only do so much in documentation. I am simply stating that the simpler and more understandable the docs are the better. This is because the "skilled" folks can skip the intro if it is obvious. I believe: "Brilliance is a mastery of the obvious" <*>>> and documentation should seek to brilliantly expose the obvious over complicated subjects.

3 2

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > > > > "Brilliance is a mastery of the obvious" <*>>> and documentation should > > seek to brilliantly expose the obvious over complicated subjects. > [David Abrahams Writes:] > Another thing: the author of documentation should (usually) disqualify > him- or herself from making judgements about understandability and > especially approachability. The problem is that once you understand > it, it's very hard to see the places where it fails to communicate to > someone who doesn't. [Brian Braatz Writes:] :) " The problem is that once you understand > it, it's very hard to see the places where it fails to communicate to > someone who doesn't." A RESOUNDING YES!!!!!!- And thank you David. This sentence is worthy of printing out and hanging on my wall. Or maybe I should make tee-shirts and hand them out at conferences. Or better yet, I could have stickers made and hand those out. Then anytime someone sees some documentation that fails to make sense to normal humans, they can slap the sticker on it and hand it back to the author.

1 0

boost cvs build failure: Unknown suffix
by Neal Becker 07 Jun '05

07 Jun '05

PYTHON_ROOT=/usr PYTHON_VERSION=2.4 bjam -sTOOLS=gcc stage Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). Unknown suffix on <@boost!libs!iostreams!build><<<<<<< - see UserObject rule in Jamfile(5).

1 1

[cvs] waiting for lock
by Pedro Lamarão 07 Jun '05

07 Jun '05

TortoiseCVS, while trying to update a working copy, has been telling me for more than an hour that it's "waiting for david_abrahams's lock in /cvsroot/boost/boost/libs/preprocessor/doc/headers/control". I'm not sure what that means besides me being currently incapable of cvs update. I'll keep trying for a while. -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business

2 2

Liquidnet is using boost
by Max Khesin 07 Jun '05

07 Jun '05

Ok, I've been waiting to say this :-), thanks for putting this page together John! Liquidnet, a financial startup and last 5th fastest growing company according to Inc is using Boost. Libraries most used, in order of importance (as if I can really measure that): shared_ptr bind boost.python lexical_cast optional any tuple regards and keep up the great work, max. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

1 0

[Iostreams] Fails to build on Windows
by Keith MacDonald 07 Jun '05

07 Jun '05

At the time of writing, Iostreams from CVS head still does not build on Windows XP, due to missing header files. The build starts with these comments: ****************************************************** Building Boost.Iostreams with bzip2 support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your bzip2 installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** ****************************************************** Building Boost.Iostreams with zlib and gzip support disabled. HINT: define the environment variable BZIP2_SOURCE to point to the root directy of your zlib installation if you have one. For more options, consult the Boost.Iostreams documentation ****************************************************** Presumably "BZIP2_SOURCE" should not effect both types of compression, and "directy" is a typo. Anyway, the following errors are then reported 8 times each: bzip2.cpp(14) : fatal error C1083: Cannot open include file: 'bzlib.h': No such file or directory zlib.cpp(14) : fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory The command line I used for the build was: bjam -sTOOLS=vc-8_0 -sICU_PATH=F:\Dev\icu-3.2 -sPYTHON_ROOT=C:\Apps\Python24 -sPYTHON_VERSION=2.4

3 8

RE: [boost] Re: [function types] Formal Review begins today.
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jody Hagins > > Well, in case you don't know MPL (although the primary audience most > > likely will) you can still have a look at the synopsis and look for > > the version with non-type template parameter... > > I would disagree with you here. Many boost users do not know MPL. Many > more probably have a cursory knowledge of MPL, but still need > documentation handy to make use of it. > > > > How do functors fit in here? If a class overloads operator(), is it > > > considered a function type? > > > > > > No. Is the definition really that unclear ? > > > > How could this probably work if operator() is a function template ? > > > > You can decompose a member function pointer to a parentheses operator > > (which implies it's already instantiated if it's a template > > function), though (after deduction or using some kind of typeof > > operator). > > No, it is clear, but I would think that some notes about operator(), > boost::function, and boost::lambda would be appropriate, since some > folks may want to use them in some ways related to function_types. > > > > > knowledge of the MPL. However, the docs seem to take too much for > > > granted, and make too many assumptions. I'd like to see more > > > detail, especially in the descriptions. > > > > What do you mean with "assumption" ? Preconditions on template > > arguments ? > > I think interface documentation should make the lowest common > assumptions. Not everyone is familiar with the types of problems this > library is trying to solve. I am sure you are not merely targeting an > audience of people who could implement this library themselves, but > those who would like this functionality without implementing the > details. > > FWIW, most boost libraries fail in this regard, in my opinion. Library > documentation should make as few assumptions about the knowledge and > experience of the user as possible. > [Brian Braatz Writes:] THANK YOU JODY- I was going to say that (grin). Allow me to add a suggestion. PICK YOUR TARGET person's skills. And then write your docs to that person. I would advocate - if you can pull it off- think about someone you know who has 2-3 years CPP experience. Think about how you would communicate your library to that person. Walk them through using the library and solving problems with the library. Assume the user knows VERY LITTLE about metaprogramming etc. Hope that helps, and thank you Jody for spending the time to write up your feedback :)

1 0

RE: [boost] Re: Re: Typeof: Review result
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Paul A Bristow > > | -----Original Message----- > | From: boost-bounces(a)lists.boost.org > | Subject: RE: [boost] Re: Re: Typeof: Review result > | > | It is not something one slaps together just to get their > | name in lights (to me at least). A boost library makes you go > | "Wow". if it doesn't make you go "Wow" it doesn't belong in boost. > [Paul A Bristow Writes:] > WOW! - What a elistist view! > > Nothing WOW about STATIC_ASSERT (for example) - but not just useful but > invaluable. > [Brian Braatz Writes:] 1- I was stating how I PERSONALLY felt about the issue. 2- The problem with thinking in the "wow" paradigm, is that is relative. STATIC_ASSERT has a wow factor to it for many. For some it does not. > IMO Boost library is about USEFULNESS and QUALITY. > [Brian Braatz Writes:] Add "efficiency" and you just described where the "wow" comes from :) > Quality code that starts by peer review AND because it is well exercised > by > lots of users on lots of different environments, and is amended often, > so is likely to be as correct as can be and as portable as practical. > [Brian Braatz Writes:] Yes > And nobody gets their names in lights - just a bucket load of hassle > manipulating their code for all the non-compliant compilers. > > Paul [Brian Braatz Writes:] HAHAHAH The underlying truth shows itself :).

1 0

[shared_ptr] dealing with shared_ptr and cycles
by Lorenzo Bettini 07 Jun '05

07 Jun '05

Hi I have this simple program, that has a class with a shared pointer to another object of the same type: #include <boost/shared_ptr.hpp> #include <string> #include <iostream> using namespace std; class C; typedef boost::shared_ptr<C> CP; class C { private: string s; CP cp; public: C(const string &ss, CP c = CP()) : s(ss), cp(c) {} void set(CP c) { cp = c; } ~C() { cout << "deleting C" << endl; } }; int main() { CP cp = CP(new C("C")); CP cp2 = CP(new C("C2")); cp->set(cp2); //cp->set(cp); cout << "use_count: " << cp.use_count() << endl;; return 0; } if I remove the comment for cp->set(cp), i.e., I set the shared_pointer to itself, there's a cycle, and thus use_count returns 2, and the object cp is never deleted (shown also by using valgrind). This is a simple program just to reproduce a much more complex situation with a data structure that deals with mutual recursive references. I do not know in advance whether the shared pointer refers to the same object or to another different object (for instance I perform also cp->set(cp2)). Now, the documentation (http://www.boost.org/libs/smart_ptr/shared_ptr.htm) says that "Because the implementation uses reference counting, cycles of shared_ptr instances will not be reclaimed. For example, if main() holds a shared_ptr to A, which directly or indirectly holds a shared_ptr back to A, A's use count will be 2. Destruction of the original shared_ptr will leave A dangling with a use count of 1. Use weak_ptr to "break cycles."" However, it is not clear to me how to use weak_ptr in this context... can some one provide some clue, please? many thanks in advance Lorenzo

6 13

RE: [boost] Re: serialization of objects with overloaded new/delete
by Andreas Brinck 07 Jun '05

07 Jun '05

Hi, > For this to work, one needs a SFINAE compiler, right? yes, perhaps the code could be modified to use the boost::enable_if utility to make it a bit clearer what's going on. > I faintly remember that early versions of the documentation (during > review) described a completely different type of support for classes > with operator new. I don't recall the details but I believe > that one was > able to specialize a template for types with operator new. > While being > slightly more cumbersome, this sort of support would work > with virtually > any compiler, not just the ones that support SFINAE. It would be > interesting to hear why this kind of operator new support was > discontinued later. I think you answered your own question. Judging from the lack of responses to my post, serializing objects with overloaded new doesn't seem to be important to most people. I guess the maintainers of the library didn't want to complicate the interface to accomodate a small minority of users. The SFINAE principle is probably the best way to handle it right now. Regards /Andreas Brinck ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/

2 1

[call traits] patch for Borland BCB6
by AlisdairM 07 Jun '05

07 Jun '05

The version check in the existing Borland workaround has not been kept up to date - see patch below: cvs diff -w boost\detail\call_traits.hpp (in directory D:\Projects\boost) Index: boost/detail/call_traits.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/detail/call_traits.hpp,v retrieving revision 1.13 diff -w -r1.13 call_traits.hpp 94c94 < #if defined(__BORLANDC__) && (__BORLANDC__ <= 0x560) --- > #if BOOST_WORKAROUND( __BORLANDC__, BOOST_TESTED_AT( 0x564 ) ) -- AlisdairM

2 1

Re: [boost] Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 07 Jun '05

07 Jun '05

In-Reply-To: <d80vqg$i5u$1(a)sea.gmane.org> daniel(a)calamity.org.uk (Daniel James) wrote (abridged): > Dave's email program has broken the threading Has it? In my browser my comments are posted to the intended part of the thread. Some of the replies have gone amiss, and some haven't. Specifically Jonathan Turkanis's replies to me have been misthreaded, but his replies to other people have too. I figured that was his email program, not mine. Are you seeing something different? My apologies to the list if so. If there is a diagnosable problem with my software I can contact the author. Feel free to reply directly if this is off-topic. -- Dave Harris, Nottingham, UK.

3 2

Borland patch for Boost Test
by AlisdairM 07 Jun '05

07 Jun '05

THe following patch should allow Borland BCB6 to pass the boost_check_equal_str test case. The problem appears to be pointer-decay of arrays. cvs diff -w boost\test\test_tools.hpp (in directory D:\Projects\boost) Index: boost/test/test_tools.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/test/test_tools.hpp,v retrieving revision 1.53 diff -w -r1.53 test_tools.hpp 285a286,296 > #if BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564)) > template<typename T, std::size_t N > > struct print_log_value< T[N] > { > void operator()( std::ostream& ostr, T const* t ) > { > ostr << t; // by default print the value > } > }; > > #endif > 333a345,354 > #if BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564)) > // Borland suffers premature pointer decay passing arrays by reference > template<typename T, std::size_t N > > struct print_helper_t< T[ N ] > { > explicit print_helper_t( T const * t ) : m_t( t ) {} > > T const * m_t; > }; > > #endif -- AlisdairM

2 1

boost book error
by Dirk Griffioen 07 Jun '05

07 Jun '05

Hi, At the moment I get the following error when I try to run my boostbook setup: xslt-xsltproc bin\msvc\debug\threading-multi\moip.doxygen.docbook xslt-xsltproc-dir html\HTML.manifest warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl" compilation error: file file:///G%3A/dev_/stl/boost_1_32_0/tools/boostbook/xsl/html.xsl line 8 element import xsl:import : unable to load http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl warning: failed to load external entity "http://docbook.sourceforge.net/release/xsl/current/html/chunk-common.xs Last saturday everything was fine. There's no firewall etc between me and http:// Has anything canged? Should I update to a newer version? Hope anyone can help, Dirk Griffioen

1 0

RE: [boost] Re: Re: Typeof: Review result
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jonathan Turkanis > Sent: Monday, June 06, 2005 4:53 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Re: Typeof: Review result > > Brian Braatz wrote: > > > Here is an idea: what-cha think- We should add a "Wow" factor to the > > lib review template. > > > > I dunno, maybe something like > > > > "Rate the WOW factor of this library:(1-5)" > > > > (now that I have made the suggestion, here comes the controversy > > (grin)) > > > > the question then becomes what if a library, gets all 1's. Does it > > still get accepted? I say no, there are plenty of "YET-ANOTHER-X" > libraries > > out there already. > > > > I say, (more controversy) that something can have a semi-boring > > functional use, but it's implementation, at the very least should have > > some "Wow" in it. > > Most people seems to agree we need a bigint library. Somehow I'm skeptical > we > can find one with a WOW factor above 2. ;-) > > Jonathan > [Brian Braatz Writes:] Hmm.. ON a serious note. It might be worth just "Capturing" the WOW factor, and using that as one piece of the "do we accept" or not puzzle.

1 0

RE: [boost] Re: Re: Typeof: Review result
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jonathan Turkanis > > Brian Braatz wrote: > > > Here is an idea: what-cha think- We should add a "Wow" factor to the > > lib review template. > > > > I dunno, maybe something like > > > > "Rate the WOW factor of this library:(1-5)" > > > > (now that I have made the suggestion, here comes the controversy > > (grin)) > > > > the question then becomes what if a library, gets all 1's. Does it > > still get accepted? I say no, there are plenty of "YET-ANOTHER-X" > libraries > > out there already. > > > > I say, (more controversy) that something can have a semi-boring > > functional use, but it's implementation, at the very least should have > > some "Wow" in it. > > Most people seems to agree we need a bigint library. Somehow I'm skeptical > we > can find one with a WOW factor above 2. ;-) > > Jonathan > [Brian Braatz Writes:] Oh I dunno, to me a big int is EXCITING (grin). :) (yes your point is in alignment with the second point I made against my own suggestion)

1 0

Re: [boost] Re: Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 07 Jun '05

07 Jun '05

In-Reply-To: <d80h47$irf$1(a)sea.gmane.org> technews(a)kangaroologic.com (Jonathan Turkanis) wrote (abridged): > array can't be given constructors without sacrificing the aggregate > initialization syntax. OK... although I'd rather have constructors than aggregate initialisation syntax. If the problem is performance, surely the compiler can optimise away the difference (given that it's a standard library component with known semantics)? Anyway, it sounds like this battle is already lost. Is there a rational for not allowing zero-sized arrays? What is the intended semantics of: array<int> a; // Or array<int,0>. assert( a.empty() ); ? Isn't this kind of thing likely to occur in generic template code? -- Dave Harris, Nottingham, UK.

4 4

RE: [boost] Re: Typeof: Review result
by Brian Braatz 07 Jun '05

07 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > > "Brian Braatz" <brianb(a)rmtg.com> writes: > > > [Brian Braatz Writes:] > > > > What are the expectations here? I find myself in this spot > > frequently. I see something up for review, and it ALWAYS happens at > > the worst time for me. I look at it, but I tend to not say much unless > > I can REALLY devote the time needed to give the library the proper > > amount of review time. > > > > There might be "no answer" to the expectations questions. But I would > > be curious how others feel about this. > > > > I.e. If I only have an hour or two to look at something- is it still > > useful for me to submit a review? > [David Abrahams Writes:] > Whenever you feel like you can say something useful. I often have > something useful to say after looking at the first few pages of > documentation. > [Brian Braatz Writes:] Good advice. After contemplating that advice, I took 20 mins to look at the function types lib- and immediately saw some issues (as you said, after the first few pages). (will write them up this evening). > > Part of the problem I have is an enormous respect for what a boost > > library is. It is not something one slaps together just to get their > > name in lights (to me at least). A boost library makes you go > > "Wow". if it doesn't make you go "Wow" it doesn't belong in boost. > > :) > > > But if I cannot devote the time needed to review something DEEPLY, I > > feel it is somewhat disrespectful for me to participate. > > > > Do you guys think I am wrong to feel this way? Or do you find the > > opinions of a quick review valuable? > > I do. > [David Abrahams Writes:] > Personally, I think too many libraries have been accepted recently > with insufficient scrutiny. There are certainly a few I would have > liked to have seen challenged along the lines of "this doesn't make me > go wow," or "does the world really need this library?" [Brian Braatz Writes:] Hmm.. Here is an idea: what-cha think- We should add a "Wow" factor to the lib review template. I dunno, maybe something like "Rate the WOW factor of this library:(1-5)" (now that I have made the suggestion, here comes the controversy (grin)) the question then becomes what if a library, gets all 1's. Does it still get accepted? I say no, there are plenty of "YET-ANOTHER-X" libraries out there already. I say, (more controversy) that something can have a semi-boring functional use, but it's implementation, at the very least should have some "Wow" in it. hmmm... I will continue to contemplate these thoughts. Hard to see the dark side is....

3 2

[mscv config]
by Thorsten Ottosen 06 Jun '05

06 Jun '05

Hi, Is there any good reason that VC++ is set to warn about ADL by default? Otherwise, we should put the equivalent of <toolset>msvc <cxxflags>/wd4675 into the main configuration for those compilers -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/

3 5

Re: [boost] Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 06 Jun '05

06 Jun '05

In-Reply-To: <42A3CF76.4040403(a)metoceanengineers.com> manfred.doudar(a)metoceanengineers.com (Manfred Doudar) wrote (abridged): > >The question for me is what the default should be. And in my view, the > >default should be safe rather than fast. > > From what I gather, and the commentary you make below, I seriously beg > to differ. Back to the year dot with C & C++ we've never had such a > thing as pre-initialization of arrays and it'd be a bad time to start > such a movement now. But std::vectors do initialise. It's the modern way :-) ("This is old and therefore good" versus "This is new and therefore better".) In my view, making the default case fast but dangerous is premature optimisation. If you need that trade-off you should request it explicitly. -- Dave Harris, Nottingham, UK.

1 0

Boost regression notification
by Douglas Gregor 06 Jun '05

06 Jun '05

Boost regression test failures ------------------------------ Report time: 2005-06-06T18:05:54Z Purpose: You are receiving this report because one of the libraries you maintain has regression test failures that are not accounted for. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 1405 failures in 14 libraries: date_time (29) filesystem (1) iostreams (8) iterator (1) multi_index (40) parameter (4) program_options (21) python (12) random (2) serialization (1262) spirit (2) test (20) thread (1) wave (2) |date_time| testgreg_serialize: gcc-3.4.3-linux gcc-4.0.0-linux testgreg_serialize_xml: gcc-3.4.3-linux gcc-4.0.0-linux testlocal_time: vc-8_0 testtime_serialize: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux mingw-3_4_2 testtime_serialize_std_config: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux mingw-3_4_2 testtime_serialize_xml: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux mingw-3_4_2 testtime_serialize_xml_std_config: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux mingw-3_4_2 |filesystem| operations_test: cw-9_5-darwin |iostreams| bzip2_test: cw-9_4 cw-9_4 code_converter_test: gcc-3.3.5-linux intel-8.1-linux gzip_test: cw-9_4 cw-9_4 zlib_test: cw-9_4 cw-9_4 |iterator| filter_iterator_test: borland-5_6_4 |multi_index| test_basic: gcc-3.4.3-linux gcc-4.0.0-linux test_capacity: gcc-3.4.3-linux gcc-4.0.0-linux test_comparison: gcc-3.4.3-linux gcc-4.0.0-linux test_composite_key: gcc-3.4.3-linux gcc-4.0.0-linux test_conv_iterators: gcc-3.4.3-linux gcc-4.0.0-linux test_copy_assignment: gcc-3.4.3-linux gcc-4.0.0-linux test_hash_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_iterators: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_modifiers: gcc-3.4.3-linux gcc-4.0.0-linux test_mpl_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_observers: gcc-3.4.3-linux gcc-4.0.0-linux test_projection: gcc-3.4.3-linux gcc-4.0.0-linux test_range: gcc-3.4.3-linux gcc-4.0.0-linux test_safe_mode: gcc-3.4.3-linux gcc-4.0.0-linux test_serialization: gcc-3.4.3-linux gcc-4.0.0-linux test_set_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_special_list_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_special_set_ops: gcc-3.4.3-linux gcc-4.0.0-linux test_update: gcc-3.4.3-linux gcc-4.0.0-linux |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 vc-7_1 |program_options| cmdline_test: borland-5_6_4 vc7 cmdline_test_dll: borland-5_6_4 vc7 parsers_test: borland-5_6_4 intel-8.1-linux vc7 parsers_test_dll: borland-5_6_4 intel-8.1-linux vc7 positional_options_test: borland-5_6_4 positional_options_test_dll: borland-5_6_4 unicode_test: vc7 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_3-darwin vc7 variable_map_test: borland-5_6_4 vc7 variable_map_test_dll: borland-5_6_4 vc7 |python| andreas_beyer: msvc-stlport indirect_traits_test: msvc-stlport vc7 numpy: gcc-3.3.5-linux polymorphism: msvc-stlport vc7 polymorphism2: msvc-stlport vc7 shared_ptr: msvc-stlport vc7 slice: gcc-3.3.5-linux vector_indexing_suite: msvc-stlport |random| random_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux |serialization| test_array_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_array_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_array_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_array_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_array_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_array_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_array_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_array_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_array_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_array_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_binary_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_binary_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_binary_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_binary_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_binary_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_binary_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_binary_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_binary_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_binary_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_binary_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_binary_archive: gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_binary_archive_dll: cw-9_4 gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_text_archive: gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_text_archive_dll: cw-9_4 gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_text_warchive: gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_xml_archive: gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_xml_archive_dll: cw-9_4 gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_xml_warchive: gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_load_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_class_info_save_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux 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_pass: gcc-3.4.3-linux gcc-4.0.0-linux test_const_save_fail1: msvc msvc-stlport vc7 test_const_save_fail2: msvc msvc-stlport vc7 test_const_save_fail3: msvc msvc-stlport vc7 test_contained_class_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_contained_class_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_cyclic_ptrs_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_delete_pointer_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_auto_ptr: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_auto_ptr_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo_exception: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo_fast_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_fast_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux msvc test_demo_pimpl: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_pimpl_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_demo_polymorphic: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_polymorphic_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo_portable_archive: cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-3_3-darwin gcc-4.0.0-linux test_demo_portable_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-3_3-darwin gcc-3_3-darwin gcc-4.0.0-linux test_demo_shared_ptr: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_demo_shared_ptr_dll: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_demo_xml: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_xml_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_xml_load: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_xml_load_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_xml_save: gcc-3.4.3-linux gcc-4.0.0-linux test_demo_xml_save_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_deque_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_deque_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_deque_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_deque_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_deque_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_ptr_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_class_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_derived_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_derived_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_derived_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_binary_archive: cw-8_3 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_text_archive: cw-8_3 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_text_warchive: cw-8_3 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_xml_archive: cw-8_3 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_xml_warchive: cw-8_3 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_diamond_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_exported_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_exported_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_list_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_ptrs_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_list_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_list_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_map_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_map_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_map_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_map_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_map_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_map_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_map_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_map_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_map_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_map_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_mi_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_mi_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_mult_archive_types: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_mult_archive_types_dll: cw-9_4 cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux msvc test_multiple_ptrs_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_multiple_ptrs_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_no_rtti_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor2_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_default_ctor_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_non_intrusive_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_null_ptr_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_nvp_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_object_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_object_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_object_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_object_text_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_object_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_object_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_object_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_object_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_object_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_object_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_optional_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_optional_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_optional_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_optional_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_optional_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_optional_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_optional_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_optional_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_optional_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_optional_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_polymorphic_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_primitive_binary_archive: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_binary_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_text_archive: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_text_warchive: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux test_primitive_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux test_primitive_xml_archive: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux mingw-3_4_2 test_primitive_xml_warchive: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux test_primitive_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux gcc-3.4.3-linux gcc-4.0.0-linux intel-8.1-linux test_private_ctor: gcc-3.4.3-linux gcc-4.0.0-linux test_private_ctor_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_recursion_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_registered_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_registered_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_reset_object_address: gcc-3.4.3-linux gcc-4.0.0-linux test_reset_object_address_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_set_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_set_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_set_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_set_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_set_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_set_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_set_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_set_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_set_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_set_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_shared_ptr_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_shared_ptr_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux msvc vc7 test_simple_class_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_ptr_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_simple_class_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_split_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_split_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_split_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_split_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_split_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_split_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_split_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_split_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_split_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_split_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_xml_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_tracking_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_traits_pass: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_binary_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_text_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_text_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_xml_archive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_unregistered_xml_warchive_dll: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_variant_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_variant_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_variant_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_variant_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_variant_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_vector_binary_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_vector_binary_archive_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux test_vector_text_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_vector_text_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_vector_text_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_vector_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_vector_xml_archive: gcc-3.4.3-linux gcc-4.0.0-linux test_vector_xml_archive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_vector_xml_warchive: gcc-3.4.3-linux gcc-4.0.0-linux test_vector_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.4.3-linux gcc-4.0.0-linux test_void_cast: gcc-3.4.3-linux gcc-4.0.0-linux test_void_cast_dll: cw-9_4 gcc-3.4.3-linux gcc-4.0.0-linux |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin |test| boost_check_equal_str: borland-5_6_4 errors_handling_test: cw-9_5-darwin vc-8_0 ifstream_line_iterator_test: gcc-3.4.3-linux gcc-4.0.0-linux mingw-3_4_2 test_fp_comparisons: borland-5_6_4 msvc msvc-stlport vc7 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin token_iterator_test: borland-5_6_4 cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux gcc-4.0.0-linux vc7 |thread| test_read_write_mutex: borland-5_6_4 |wave| testwave: cw-8_3 cw-9_5-darwin

2 1

[ptr_container] linking errors
by Felipe Magno de Almeida 06 Jun '05

06 Jun '05

Hi, I'm having linking errors(multiple definitions) with the ptr_map in VC7.1. The problem is in the struct eraser(all its methods) inside the function insert_lookup in the ptr_map_adapter_base template. I've tried inlining all the methods with no success. The workaround I found was making eraser a inner class inside the ptr_map_adapter_base template(moved it from the insert_lookup function). This errors appear when using the operator[] of the very same ptr_map in two different files. I attached the simplest files that I could make that shows these problems... Thank you for boost, Felipe Magno de Almeida. -- Felipe Magno de Almeida Developer from synergy and Computer Science student from State University of Campinas(UNICAMP). Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br "There is no dark side of the moon really. Matter of fact it's all dark."

3 3

RE: [boost] Who's Using Boost?
by Brian Braatz 06 Jun '05

06 Jun '05

this is AWESOME. a HUGE THANK YOU for putting this together. Extremely cool. This will definitely help with folks trying to "get permission" to use boost in their company. > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of John Maddock > Sent: Monday, June 06, 2005 4:23 AM > To: Boost mailing list > Subject: [boost] Who's Using Boost? > > There are now a set of prototype "Who's Using Boost?" pages available at: > > http://freespace.virgin.net/boost.regex/who/html/index.html > > Comments and suggests welcome, but in particular we need more case > studies/products etc that are using Boost to be listed. If you have a > product or project that could be listed then please see the submission > guidelines at: > > http://freespace.virgin.net/boost.regex/who/html/who_s_using_boost_/subm it > .html > > Regards, > > John. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Regression, fixes, and stuff
by Pedro Lamarão 06 Jun '05

06 Jun '05

Hello all. I've been playing more intimately with boost lately, and running the regression tests. As I do it, I feel I'll have the time to help fixing bugs here and there. But I wouldn't like to just start throwing patches in the list risking entering in conflict with other people's work. So... How is the development process coordinated? Do regressions get bugs assigned to them? Is there a list for sending patches? -- Pedro Lamarão Desenvolvimento Intersix Technologies S.A. SP: (55 11 3803-9300) RJ: (55 21 3852-3240) www.intersix.com.br Your Security is our Business

2 1

compressed_pair requirements?
by David Abrahams 06 Jun '05

06 Jun '05

Can arguments to compressed_pair be const-qualified? The documentation only lists this restriction: Note that compressed_pair can not be instantiated if either of the template arguments is a union type, unless there is compiler support for boost::is_union, or if boost::is_union is specialised for the union type. I believe I am getting an error from Intel C++ when an argument to compressed_pair is const. The question is whether we need a workaround in compressed_pair.hpp or a change to the html documentation. -- Dave Abrahams Boost Consulting www.boost-consulting.com

6 22

Re: Typeof: Review result
by Tom Brinkman 06 Jun '05

06 Jun '05

Andy Little wrote: > Three positive reviews is not sufficient in my opinion. However, > the precedent has already be set, as other libraries have been approved on > a similar limited number of reviews. >>Obvious questions in response to this... >>How many reviews are sufficient? >> What proportion in favour/against acceptance is acceptable? The judgement of the library's review manager is the final determinent. The criteria that he/she used to accept or reject the submission should be clearly stated in the review managers report after the review period is over. Tom Brinkman

6 5

[lambda] how can I access structure member
by Rafal Dabrowa 06 Jun '05

06 Jun '05

Suppose I have the following structure: struct xy { int x, y; }; and the following vector: vector<xy> v(10); I want to use lambda library for find an item in the table. Let's say, with x member value equal to 10. Something like this doesn't work: pos = find_if(v.begin(), v.end(), _1.x == 10); How the above line should be written ? Rafal

2 1

[assign][range][ptr_container] using-induced problem
by Joaquín Mª López Muñoz 06 Jun '05

06 Jun '05

Martin Wille posted about this a couple of days ago (http://lists.boost.org/boost-testing/2005/05/1216.php) but I'm afraid it could have passed unnoticed. Some tests from Boost.(Assign|Range|PointerContainer) have the following layout #include<...> using namespace std; using namespace boost; ... #include <boost/test/unit_test.hpp> having the using directives before boost/test/unit_test.hpp is AFAICS illegal and does indeed cause problems with GCC 3.4.x and GCC 4.x, see for instance http://tinyurl.com/8payc I cannot test it, but I guess it suffices to move all the includes before any using directive. This will probably clear up dozens of tests, including some toolsets that are currently marked as unusable. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

4 10

Math constants - updated.
by Paul A Bristow 06 Jun '05

06 Jun '05

I have recently posted to the Boost Sandbox vault an update of my collection of mathematical constants, previously reviewed as a Boost library and ultimately not accepted because of lack of agreement on how to present the constants, especially for User Defined Types, and an outbreak of macrophobia. However the values are still valid and some may find them a useful and convenient source, with even more reassuringly sufficient decimal places to give you a warm feeling ;-) The values are take from Internet sources and then computed with NTL a arbitrary (very high) precision library and presented as 40 decimal digit strings, suitable for all hardware as yet envisioned. I have tried to check as many as possible against two source to try to avoid mistakes, but please tell me of any that you find. The same values are actually presented in header files as macros, floats, doubles, and long doubles, (and also as the functions allowing pi to call a function pi() proposed by Michael Kenniston, even though I am not entirely convinced of their usefulness). So including double_constants.hpp will give lots of values, for example: static const double cubeRootTwo = 1.25992104989487316476721060727822835057; // 2^1/3 If you prefer a macro, the define_constants.h will give you values like #define M_EPOWPI 23.14069263277926900572908636794854738027L /* e^pi */ You can of course also cut and paste invididual lines, if you just want pi. No choice of names will suit everyone - so I have indulged myself. You can change them of course. http://tinyurl.com/7p6es for two zips of headers and documentation as html. Enjoy? Paul PS Some of these values are to be used in the math functions for stats library that I am in danger of getting around to Real Soon Now. Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com

10 44

Re: [boost] Re: Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 06 Jun '05

06 Jun '05

In-Reply-To: <d7iigr$7tn$1(a)sea.gmane.org> technews(a)kangaroologic.com (Jonathan Turkanis) wrote (abridged): > boost::array is just supposed to give built-in arrays a container > interface. Built-in arrays never have size 0, so I don't see > why boost::arrays should. Surely built-in arrays can have size 0? For example: int n = 0; int *array = new int[n]; In my experience it is important to handle zero edge-cases correctly and uniformly. I have been reading: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1479.html and I don't understand the reasoning there. Personally I'd rather change the language so that: const int n = 0; int array[n]; was acceptable too, making the static case consistent with the dynamic case and both consistent with n>0. Even if this glitch is not fixed (because it requires a language change), I'd rather an array library not perpetuate the problem. For example: array<T,0> a; could allocate a single byte of memory with alignment suitable for T. At worst, sizeof(T) bytes could be allocated, but no T should be constructed. -- Dave Harris, Nottingham, UK.

2 1

Boost Array Initialization Technique
by christopher diggins 06 Jun '05

06 Jun '05

The fact that the Boost array class does not support constructors in favour of the limited and somewhat obscure aggregate initialization syntax has me concerned. IMO it would be much more flexible and powerful to support overloading of the comma operator. The following works on Visual C++ template<typename array_T, unsigned int N> struct array_comma_helper { array_comma_helper(array_T& x) : m(x) { } array_comma_helper(const array_comma_helper& x) : m(x.m) { } array_comma_helper& operator=(typename array_T::value_type x) { m[0] = x; return *this; } mutable array_T& m; }; template<class array_T, unsigned int N, class Scalar_T> array_comma_helper<array_T, N+1> operator,(array_comma_helper<array_T, N> h, const Scalar_T& x) { array_comma_helper<array_T, N+1> ret(h.m); ret.m[N + 1] = x; return ret; } template<class array_T> array_comma_helper<array_T, 0> initialize(array_T& x) { return array_comma_helper<array_T, 0>(x); } This enables us to write: int n = 2; array<int, 3> a; initialize(a) = 1, n, 3; This is much more flexible and it allows us to have constructors in boost::array thus making it a full reversible container. Christopher Diggins http://www.cdiggins.com

15 36

Re: [boost] Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 06 Jun '05

06 Jun '05

In-Reply-To: <20050601173608.GA77601(a)compsoc.man.ac.uk> cow(a)compsoc.man.ac.uk (Jonathan Wakely) wrote (abridged): > Actually, it's moot because it's been semi-standardised in TR1, not > because you now understand the design goals ;) Really? My impression was that TR1 had not been reviewed in detail. When the hashing library was submitted to boost, I understood it to be the same as TR1 yet we found several problems with it. We did not blindly accept it just because it was in TR1. -- Dave Harris, Nottingham, UK.

4 4

stride iterators and matricies
by christopher diggins 06 Jun '05

06 Jun '05

Well all of this talk of matricies, and what not got me thinking that perhaps we should get back to basics and introduce stride iterators into Boost which properly model the Random Access Iterator concept (unless they are already existant somewhere and I simplty overlooked them :-p ) I would suggest that we introduce a mini-library simply for stride iterators (and k-stride iterators, where the stride factor is a compile-time constant.) Any interest in seeing the following stride iterators submitted to boost as a mini-library? // public domain by Christopher Diggins #ifndef CDIGGINS_STRIDE_ITER_HPP #define CDIGGINS_STRIDE_ITER_HPP #include <iterator> namespace cdiggins { template<class Iter_T> class stride_iter { public: // public typedefs typedef typename std::iterator_traits<Iter_T>::value_type value_type; typedef typename std::iterator_traits<Iter_T>::reference reference; typedef typename std::iterator_traits<Iter_T>::difference_type difference_type; typedef typename std::iterator_traits<Iter_T>::pointer pointer; typedef std::random_access_iterator_tag iterator_category; typedef stride_iter self; // constructors stride_iter() : m(null), step(0) { }; explicit stride_iter(Iter_T x, difference_type n) : m(x), step(n) { } // operators self& operator++() { m += step; return *this; } self operator++(int) { self tmp = *this; m += step; return tmp; } self& operator+=(difference_type x) { m += x * step; return *this; } self& operator--() { m -= step; return *this; } self operator--(int) { self tmp = *this; m -= step; return tmp; } self& operator-=(difference_type x) { m -= x * step; return *this; } reference operator[](difference_type n) { return m[n * step]; } reference operator*() { return *m; } // friend operators friend bool operator==(const self& x, const self& y) { return x.m == y.m; } friend bool operator!=(const self& x, const self& y) { return x.m != y.m; } friend bool operator<(const self& x, const self& y) { return x.m < y.m; } friend difference_type operator-(const self&x, const self& y) { return x.m - y.m; } friend self operator+(const self&x, difference_type y) { return stride_iter(x) += y; } friend self operator+(difference_type x, const self& y) { return stride_iter(y) += x; } private: Iter_T m; difference_type step; }; template<class Iter_T, int Step_N> class kstride_iter { public: // public typedefs typedef typename std::iterator_traits<Iter_T>::value_type value_type; typedef typename std::iterator_traits<Iter_T>::reference reference; typedef typename std::iterator_traits<Iter_T>::difference_type difference_type; typedef typename std::iterator_traits<Iter_T>::pointer pointer; typedef std::random_access_iterator_tag iterator_category; typedef kstride_iter self; // constructors kstride_iter() : m(NULL) { } explicit kstride_iter(Iter_T x) : m(x) { } // operators self& operator++() { m += step(); return *this; } self operator++(int) { self tmp = *this; m += Step_N; return tmp; } self& operator+=(difference_type x) { m += x * Step_N; return *this; } self& operator--() { m -= step(); return *this; } self operator--(int) { self tmp = *this; m -= Step_N; return tmp; } self& operator-=(difference_type x) { m -= x * Step_N; return *this; } reference operator[](difference_type n) { return m[n * Step_N]; } reference operator*() { return *m; } // friend operators friend bool operator==(const self& x, const self& y) { return x.m == y.m; } friend bool operator!=(const self& x, const self& y) { return x.m != y.m; } friend bool operator<(const self& x, const self& y) { return x.m < y.m; } friend difference_type operator-(const self&x, const self& y) { return x.m - y.m; } friend self operator+(const self&x, difference_type y) { return stride_iter(x) += y; } friend self operator+(difference_type x, const self& y) { return stride_iter(y) += x; } private: Iter_T m; }; } #endif Christopher Diggins http://www.cdiggins.com

7 18

[promotion]
by Matt Hurd 06 Jun '05

06 Jun '05

I remember a previous thread lamenting knowledge of boost for both peddling skills and promoting its use within a company. Perhaps another possibility for boost might be an area for advertising positions vacant for boosters. I have a couple of couple of positions now in Sydney in my company and boosters are thin on the ground. I'm toying with the idea of requiring them to contribute to boost as part of their employment, but that may be just my own guilt regarding my lack of contribution. I expect to hire a couple of people that don't know boost exists if previous experience is repeated. I don't know the best way to find boosters and if they are like me they are too busy working to read ads anyway. Such a job area at boost indirectly supports the value proposition of using boost if the skills are seen to have demand. A lot of people learn .NET or Java as this is where the careers seem to be. Then again goodness for goodness sake is perhaps more valuable. I can see both sides so I'm not sure. I also thought that perhaps the large number of hits boost gets could be put to good use with some google ads, banners, or some such, but I'm not sure I'd like to see boost cluttered with advertising. Raises the question of what the monies would be used for anyway. I would also worry it would dilute the nice volunteer collegial ethic that is usually seen around these parts. It that process starts perhaps you inevitably end up with something more like an Apache foundation structure? Dunno. Any thoughts? $0.02 matt matthurd(a)acm.org

2 1

Submissions
by Detlef Meyer-Eltz 06 Jun '05

06 Jun '05

Hello, I would be glad if you would put my program into your list The name of the Application --------------------------- TextTransformer The name of the company ----------------------- Dr. Detlef Meyer-Eltz A paragraph describing the Application: --------------------------------------- The TextTransformer is a Windows IDE for the generation of top down parsers with included c++ interpreter code for semantic actions. Both can be executed or debugged immediately on single source files or on groups of files. Generated parsers can be exported as c++ code including as well the interpretable code as any arbitrary other code. Tokens are defined as POSIX regular expressions and rules are defined in a similar syntax quasi as regular expressions of regular expressions. The construction of parse trees and their traversal is supported. parts of Boost used ------------------- The TextTransformer is essentially based on the boost regex library, by which the tokens for a parser can be defined. The lexical_cast and the format library are used for the integrated c++ interpreter. For the future also an interpreter version of the string_algo part is planned. The program_options library will be used too to improve the command line version of the texttransformer. URL's to your companies home page --------------------------------- http://www.texttransformer.com Download -------- http://www.texttransformer.com/downloads/setup.exe Thank you very much for your work Detlef Meyer-Eltz -- mailto:Meyer-Eltz@t-online.de url: http://www.texttransformer.de url: http://www.texttransformer.com

1 0

[shmem] New Shmem snapshot in boost vault[retry]
by Ion Gaztañaga 06 Jun '05

06 Jun '05

Hi to all, I sent this yesterday, but I don't see it in the list so I'm resending it again. If previous mail arrives, please forgive me for the duplication: I've just uploaded a new Shmem snapshot to boost vault. Not many changes but it was time to upload the little changes. -> Fixed gcc 3.3.x warnings Caleb pointed out. -> Revised documentation. -> New shared memory container: boost::shmem::deque<> Tested in Visual 7.1/Winxp and gcc 3.4/suse linux 9.3. Remember that Shmem uses unordered associative containers in some tests to make sure that Daniel's hash_map is shared memory friendly. Unordered containers are also in boost vault. Documentation is also online here: http://ice.prohosting.com/newfunk/boost/libs/shmem/index.html Any comment or suggestion is welcome. Regards, Ion

1 0

[program_options] Patch for Tru64/cxx65
by Markus Schöpflin 06 Jun '05

06 Jun '05

Attached patch fixes the last failure on Tru64. (See http://tinyurl.com/dfslr) Ok to commit? Markus Index: parsers_test.cpp =================================================================== RCS file: /cvsroot/boost/boost/libs/program_options/test/parsers_test.cpp,v retrieving revision 1.12 diff -u -w -r1.12 parsers_test.cpp --- parsers_test.cpp 27 Apr 2005 07:02:39 -0000 1.12 +++ parsers_test.cpp 17 May 2005 10:12:16 -0000 @@ -126,7 +126,13 @@ // Regression test: check that '0' as style is interpreted as // 'default_style' vector<option> a4 = - parse_command_line(5, cmdline3_, desc, 0, additional_parser).options; + parse_command_line(5, +#if BOOST_WORKAROUND(__DECCXX_VER, BOOST_TESTED_AT(60590042)) + static_cast<char const * const *>(cmdline3_), +#else + cmdline3_, +#endif + desc, 0, additional_parser).options; BOOST_CHECK_EQUAL(a4.size(), 4u); check_value(a4[0], "foo", "4");

3 5

Re: [boost] Re: Boost Array Initialization Technique
by brangdon＠cix.compulink.co.uk 06 Jun '05

06 Jun '05

In-Reply-To: <005501c566b3$1fc76eb0$2b792518@heronnest> cdiggins(a)videotron.ca (christopher diggins) wrote (abridged): > > I strongly disagree. Forcing initialization makes code that is not > > useful for high performance numerical processing. When we declare a > > container of 1000000 elements, we don't want to waste time > > initializing each, unless we want to. > > I think the best solution in this case is to use an alternative > "collection" for numerical processing. Using a class intended as > general purpose array for numerical processing I think would not be a > good idea. I doubt we need a whole class. A special argument might do, to let us choose: boost::array<int,1000> b( boost::uninitialised ); boost::array<int,1000> b( boost::initialised ); The question for me is what the default should be. And in my view, the default should be safe rather than fast. ---- For what it's worth, I think auto variables, std::complex and even std::vector should be the same: initialised by default but with uninitialised available as an option. And since this is now a language change, perhaps "boost::initialised" should be spelt "?" for brevity. int x; // x == 0. int y = ?; // y is uninitialised. int *px = new int; // *px == 0. int *py = new int( ? ) // *py is uninitialised. vector<int> vx( 100 ); // vx.front() is 0. vector<int> vy( 100, ? ); Vectors are complicated in that their elements currently need to be copyable. Either the standard needs to specify when they are copied, so that eg vy is OK as long as the vector is not resized; or else it could make initialisation implementation-defined in the ? case. Then on most platforms, vector<int> would not need initialisation but vector<double> would. User code would not be able to tell the difference. Basically, initialising with ? is telling the implementation that the user will always write to the variable before reading it. The implementation exploits that knowledge as best it can. -- Dave Harris, Nottingham, UK.

4 3

Boost Build Env Checker (was RE: [boost] Re: Customer Friendlier Boost Installation)
by Brian Braatz 06 Jun '05

06 Jun '05

David- Some thoughts below (sorry for taking a bit to come back on this one. I have been contemplating) > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > Sent: Tuesday, May 31, 2005 7:08 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Customer Friendlier Boost Installation > > "Brian Braatz" <brianb(a)rmtg.com> writes: > > > HAVING said that here is the suggestion, reformed: > > > > Boostenvcheck.exe become s a program which LISTS the dependencies for > > your configuration. > > Can you show an example of what that output might look like? I don't even > have a clear idea of what you mean by "dependencies" or "your > configuration." [Brian Braatz Writes:] I must say, I need to fully absorb how bjam \ boost.build interoperate, until doing so, please understand the details of this idea maybe ill formed. I get it conceptually, but it is still a "black box" in my head. At a high level all I am talking about is the same style of thinking that goes into coding a unit test being applied to a runtime environment. maybe if I provide a different context: (to at least describe the style of thinking I am espousing) lets say I have developed a command line compiler that has a series of dependencies: * INCLUDE var needs to be set to a valid path * We assume some standard files are available here (stdio.h etc) * LIB var needs to be set to a valid path * we assume some standard lib files- or Maybe just assume there is at least ONE lib file there lets say I have shipped my compiler to the masses, and soon I get reports from the users that they have funky errors when trying to compile something. Most of the time, it is USER error. In fact frequently, I may spend hours on the phone with them only to discover they did not configure something correctly or set it up properly. in my frustration over time wasted I decide to write a env checker for my compiler. ill call it clenvcheck.exe. when you run clenvcheck, if I elected to be extreme, I would: 1- validate INCLUDE and LIB vars are set 2- Read the contents of dirs to ensure some or all of the required core files exist 3- display a list of these "dependencies" in my output report i.e. "found stdio.h at c:\brianscompiler\include" 4- check to see if I can find my linker- send the version and location of it to the report 5- display a HIGH Level message denoting whether the "environment passed the test" for my compiler. so armed with this new tool I can now, when talking with folks over the phone, ask them to run the report. when it says "passed"- I can quickly re-direct them back to their code. if they are not convinced, I can have them send me the report and I can look at it and try to determine where the issue is. ADDTIIONAL scenario: Lets say, in my compiler business, I have a scenario where I occasionally release to the users a bug fixed header file. I send out a mail with the new file and explicit instructions on where to put it. After I have released a few bug fixed header files, I find users complaining about weird problems. Turns out, I am now back to spending an dreadful amount of time on the phone only to discover 9 times out of 10 the user did not follow instructions. 1 time out of 10 there actually was a bug in something I released. 10 times out of 10, the customer is frustrated. Even if the customer REALIZES THEY made the mistake, it still leaves them frustrated with ME and my PRODUCT. So I elect to get a bit more extreme in my env checker. I upgrade it so that it adds to the report a hash of all the "things it depends on", i.e. header files, link.exe etc. So now, when the user has a problem, I have them send me the report. I can also make available to them a list of the hashes for the files which I have tested to "work". I spend less time supporting my product, and my customers are happier because I can keep them running much more effectively. I have put a system in place to "Introspect" the users environment. By doing so, I have decreased the amount of time I have to spend introspecting manually. HOW THIS RELATES TO BOOST.BUILD: I need to understand boost.buiid better to give a better suggestion. Hopefully my example might inspire the "Dependancies" to shake out, even if I do not fully understand boost.build yet. I believe this STYLE of thinking can be applied, but I have to get my current boost things done before I can start down this track. As I said before, if the thinking here inspires someone to START something like this all the better . :) IF NOT, I intend on tackling this in the future. (I first have to become a expert in boost.build though :)) I would like to eventually see something that allows someone to SPIT out a report, mail it to the list, and have the people on the list be able to IMMEDIATELY tell the person what could be horked, or why it is not building for them. Cheers, Brian "The Village Idiot" Braatz

2 1

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 06 Jun '05

06 Jun '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > > I have read the MPL book now FIVE TIMES cover to cover. On the fith > > pass, I "saw it". (the mpl::for_each<> is what kicked it in for me) > > Wow, I applaud your fortitude and apologize for writing something that > took you so long to "see." [Brian Braatz Writes:] Hmm.... I believe the MPL book is an excellent body of work. The difficulty is because 1- I am either VERY smart about a subject or it is a black box. there seems to be little middle ground (this is learning style I think) 2- Metaprogramming is "training your brain" to think differently. Honestly with the subject matter being so DIFFERENT from what us normal blokes are used to, I am not sure if I could even suggest a better way to present it. Being able to write compile time code is a skill that belongs to people who have the commitment to struggle through and learn it. the TWISTED thing, is as I am getting more and more, it feels natural. Also I think I am wearing out my copy of the book- I continually go back and re-read sections and chapters. THANKS to both you and Aleksey for birthing that sucker. Lots of good information in there. TO ANYONE READING THIS BOOK: DON'T GIVE UP. KEEP AT IT. YOU WILL GET IT. You just have to read it enough that you begin to bleed through your eyes. When that happens, you know you are close......

2 1

[parameter] Patch for Tru64/CXX65
by Markus Schöpflin 06 Jun '05

06 Jun '05

Hello, attached patch fixes the current regression failure for the basics test. The code in questions contains a non-working workaround for this compiler, the patch removes this workaround as well. Ok to commit? Markus Index: basics.cpp =================================================================== RCS file: /cvsroot/boost/boost/libs/parameter/test/basics.cpp,v retrieving revision 1.8 diff -u -r1.8 basics.cpp --- basics.cpp 16 May 2005 12:58:48 -0000 1.8 +++ basics.cpp 3 Jun 2005 16:29:10 -0000 @@ -14,7 +14,6 @@ namespace test { - // A separate function for getting the "value" key, so we can deduce // F and use lazy_binding on it. template <class Params, class F> @@ -39,8 +38,13 @@ typename boost::parameter::binding< Params, index_, int - >::type i = p[index | 999]; - + >::type i = +#if BOOST_WORKAROUND(__DECCXX_VER, BOOST_TESTED_AT(60590042)) + p[test::index | 999]; +#else + p[index | 999]; +#endif + p[tester](n,v,i); return 1; Index: basics.hpp =================================================================== RCS file: /cvsroot/boost/boost/libs/parameter/test/basics.hpp,v retrieving revision 1.2 diff -u -r1.2 basics.hpp --- basics.hpp 15 May 2005 10:15:56 -0000 1.2 +++ basics.hpp 3 Jun 2005 16:29:10 -0000 @@ -88,13 +88,6 @@ { return values_t<Name,Value,Index>(n,v,i); } - -#if defined( __DECCXX_VER ) - && BOOST_WORKAROUND(__EDG_VERSION__, BOOST_TESTED_AT(245)) - // Some kind of nasty ambiguity arises here -- is there an index in - // the global namespace? - using test::index; -#endif } // namespace test

2 2

RE: [boost] Re: ICE ICE BABY! (my MPL code is ICEing)
by Brian Braatz 05 Jun '05

05 Jun '05

> >> > >>template <class type_t, class sequence_t> > >>struct copy_col_if_in_dest > >>: public if_< typename is_same< typename deref<typename > >>boost::mpl::find<sequence_t, type_t>::type >::type, type_t>, > > > > do_copy_col, > > > >>do_not_copy_col>::type > >>{ > >>}; > > This code has a problem when type_t is not in sequence_t: the > past-the-end iterator gets dereferenced. I wrote a short program to do > what you want (it's more explicit, it uses mpl::contains<>): > > #include <boost/mpl/vector.hpp> > #include <boost/mpl/if.hpp> > #include <boost/mpl/contains.hpp> > > namespace mpl = boost::mpl; > > struct do_copy_col {}; > struct dont_copy_col {}; > > template<typename T, typename Seq> > struct copy_col_if_in_dest > : mpl::if_< > mpl::contains<Seq, T>, > do_copy_col, > dont_copy_col > >::type > { > }; > > int main() > { > typedef mpl::vector<char, short, int, long> v; > do_copy_col do_copy = copy_col_if_in_dest<int, v>(); > dont_copy_col dont_copy = copy_col_if_in_dest<bool, v>(); > return 0; > } > [Brian Braatz Writes:] Wow. Many THANKS- the mpl::contains<> is REALLY what I was looking for. (Though the exercise of doing it with if_<> was a useful experience) THANK YOU ( I have been burning the morning and afternoon oil here the last few weeks trying to get a lib I am proposing ready for boost people to look at) -I am going to replace the code I had with the code you presented, and make a note of your contribution. THANKS AGAIN! Brian

1 0

problems buidling latest cvs version
by Christopher Lux 05 Jun '05

05 Jun '05

hi, bjam cancels buidling in v1 and v2 mode on the latest cvs checkout. i used bjam built from the source from the checkout. error message said: Building Boost.Regex with the optional Unicode/ICU support disabled. Please refer to the Boost.Regex documentation for more information (and if you don't know what ICU is then you probably don't need it). C:\_development\boost_cvs\tools/build/v1\boost-base.jam:1966: in subvariant-target *** argument error * rule library-file ( target : sources + ) * called with: ( <@boost!libs!iostreams!build\libboost_iostreams.lib\vc-7_1\debug\runtime-link-static>libboost_iostreams-vc71-sgd-1_33.lib : ) * missing argument sources C:\_development\boost_cvs\tools/build/v1\boost-base.jam:119:see definition of rule 'library-file' being called C:\_development\boost_cvs\tools/build/v1\boost-base.jam:2403: in stage Jamfile:195: in load-jamfiles C:\_development\boost_cvs\tools\build\v1\bootstrap.jam:21: in boost-build C:\_development\boost_cvs\boost-build.jam:16: in module scope

1 0

[typeof] Small feature request
by Pavel Chikulaev 05 Jun '05

05 Jun '05

Hi all, I've got a small feature request to type_of library: 1) BOOST_TYPEOF_CONSTANT_COMPLEXITY Macro is defined if typeof can't evaluated with constant complexity 2) BOOST_TYPEOF_LINEAR_COMPLEXITY Macro is defined if typeof can't evaluated with linear complexity -- Pavel Chikulaev

2 2

[1.33] recent check-ins break date-time serialization tests
by Jeff Garland 05 Jun '05

05 Jun '05

I didn't look at the check-in logs, but in the last 24-48 hours a host of previously passing date-time serialization tests have started to fail. In particular code warrior 9-4, various gcc, and vc7 were previously passing. I haven't made any check-ins to date-time, so unless someone else has I expect the problem is elsewhere... summary: http://tinyurl.com/ayl5j detailed example: http://tinyurl.com/e2pa5 Jeff

4 4

boost::lock_error - documentation bug
by Paul Groke 05 Jun '05

05 Jun '05

Hi everybody, there seems to be a bug in the documentation (or implementation?) of boost::lock_error. The documentation (http://www.boost.org/doc/html/lock_error.html) describes lock_error as: Synopsis: class lock_error : public std::logical_error { ... Whereas them implementation (1.32.0, thread/exceptions.hpp) declares boost::lock_error as derived from boost::thread_exception which is derived from std::exception and nothing more. Even assuming std::logic_error was ment (there is no class std::logical_error ) I'd say that's a documentation bug. I haven't looked through all the other exception classes defined by boost::thread ... maybe someone should :-) bye, Paul

1 0

RE: ICE ICE BABY! (my MPL code is ICEing)
by Brian Braatz 04 Jun '05

04 Jun '05

HAHAHAHA Nevermind. copy_col_if_in_dest<boost::mpl::at<src::typelist, boost::mpl::int_<0> >::type,src::typelist>(); instead of being src::typelist (which is a ref to the param of type src_t) it needs to be src_t::typelist. it was indeed something stupid- I am undecided as to which is more stupid. The fact that I didn't catch that or the fact that MSVC ICE'd on it...... sorry for bugging you guys > -----Original Message----- > From: Brian Braatz > Sent: Saturday, June 04, 2005 2:38 PM > To: 'boost(a)lists.boost.org' > Subject: ICE ICE BABY! (my MPL code is ICEing) > > Sitting in the backyard. > > Beautiful day, got up at 3am to get something figured out (for proposed > boost profiler \ introspection library). > > Good news is I figured out the MPL code needed to accomplish my goal. > After typing in an incremental version of the code, I got the dreaded > internal compiler error (ICE). > > I am chewing on this- and thought I would post it so to provide an > opportunity for someone to show how incredibly stupid I am because I did > something that was obviously wrong. (you can even rub my nose in it if you > like :) ) > > here is the code: > > I am tearing it apart\deconstructing to try to figure out what is kicking > in the ICE. (I am also going to try it with an eval_if (which I should be > using anyway) just to see what happens) > > I am using boost 1.32 and vc7.1 > > struct do_copy_col > { > typedef do_copy_col type; > do_copy_col() > { > std::cout << "do_copy_col" << std::endl; > } > // todo- implement operator()(dest,src) > }; > struct do_not_copy_col > { > typedef do_not_copy_col type; > do_not_copy_col() > { > std::cout << "do_not_copy_col" << std::endl; > } > > // todo- implement operator()(dest,src) > }; > > template <class type_t, class sequence_t> > struct copy_col_if_in_dest > : public if_< typename is_same< typename deref<typename > boost::mpl::find<sequence_t, type_t>::type >::type, type_t>, do_copy_col, > do_not_copy_col>::type > { > }; > > template <class src_t, class dest_t> > void copy_union(src_t & src, dest_t & dest) > { > copy_col_if_in_dest<boost::mpl::at<src::typelist, boost::mpl::int_<0> > >::type,src::typelist>(); > }

2 1

ICE ICE BABY! (my MPL code is ICEing)
by Brian Braatz 04 Jun '05

04 Jun '05

Sitting in the backyard. Beautiful day, got up at 3am to get something figured out (for proposed boost profiler \ introspection library). Good news is I figured out the MPL code needed to accomplish my goal. After typing in an incremental version of the code, I got the dreaded internal compiler error (ICE). I am chewing on this- and thought I would post it so to provide an opportunity for someone to show how incredibly stupid I am because I did something that was obviously wrong. (you can even rub my nose in it if you like :) ) here is the code: I am tearing it apart\deconstructing to try to figure out what is kicking in the ICE. (I am also going to try it with an eval_if (which I should be using anyway) just to see what happens) I am using boost 1.32 and vc7.1 struct do_copy_col { typedef do_copy_col type; do_copy_col() { std::cout << "do_copy_col" << std::endl; } // todo- implement operator()(dest,src) }; struct do_not_copy_col { typedef do_not_copy_col type; do_not_copy_col() { std::cout << "do_not_copy_col" << std::endl; } // todo- implement operator()(dest,src) }; template <class type_t, class sequence_t> struct copy_col_if_in_dest : public if_< typename is_same< typename deref<typename boost::mpl::find<sequence_t, type_t>::type >::type, type_t>, do_copy_col, do_not_copy_col>::type { }; template <class src_t, class dest_t> void copy_union(src_t & src, dest_t & dest) { copy_col_if_in_dest<boost::mpl::at<src::typelist, boost::mpl::int_<0> >::type,src::typelist>(); }

1 0

Function type to function call, how to?
by Arkadiy Vertleyb 04 Jun '05

04 Jun '05

Hi all, I was trying to come up with a useful example of LVALUE_TYPEOF, so I decided to implement the "trace" function from the motivation section of decltype/auto proposal. However I ran into unexpected problem: Given a function type F, and parameter type T, how to create an expression for typeof to use in the return type? I use VC71, and the only thing that seems to work (but with a warning) is: F()(T()) The warning is something about using a null pointer to call a function... *(F*)0 doesn't work, and something like make<F>() doesn't work either -- 'expression can't be evaluated to a function call with one parameter', or something like this. What would be the correct way of doing this, and is there one? Thanks in advance. Regards, Arkadiy

3 5

Re: Typeof: Review result
by Tom Brinkman 04 Jun '05

04 Jun '05

Jonathan Turkanis wrote: > Another easy improvement would be to add accepted libraries under a > probation or beta period of say six months. The library would remain > beta until its stable enough and has additional time for more user > scrutiny. A prominent boost member would make the judgement about > when to remove the library from its beta period. During the beta > period, the library author would be asked to complete the libraries > documentation, examples and requested changes from the additional user > scrutiny. >> Why make a library which has been in development for a long time and has >> received intense scrutiny undergo a probationary period? When a library is in the beta period, the author could change the public interfaces based upon the usablity concerns of its users. In some cases, as most library's take many-many months to fully appreciate and learn, this could be a benefit. I see that the term "beta" is ubiquitious and basically means that the "technology" is in active development and may change before its final release. Labeling newly accepted libraries as "beta" for a time would give the libfrary author more time to refine the submission. > If there are no objections, I will start requesting that libraries > under review be sponsered by at least prominent boost member. This > would ensure that accepted libraries meet the approval of a least one > prominent boost member. >> This sounds similar to the mentoring idea that was proposed after the >> >> OOPSLA meeting. I think it's a good idea, as long as you expand the list of >> "prominents" to include all active library authors and maintainers. Agreed. Review Wizard, Tom Brinkiman Jonathan

3 2

Re: stride iterators and matricies
by Sam Saariste 04 Jun '05

04 Jun '05

"Peter Dimov" <pdimov(a)mmltd.net> wrote in message news:<001001c5686f$8c19d950$6501a8c0@pdimov>... > Neal Becker wrote: > > > Here's my version: > > [...] > > One interesting problem with strided iterators is coming up with end values. > Suppose you have > > int x[ 4 ]; > > and you want to iterate over x[1] and x[3] with stride 2. Your begin > iterator will be x+1, and your end iterator will be x+5 - an invalid > address. > I don't think end values are a difficult problem as long as the size of the range is guaranteed to be a multiple of the stride and I have always found this to be a reasonable restriction. In addition to the stride, the iterator interface does need an offset parameter. In your example the size of the range is indeed a muliple of the stride, so there is a simple solution: store the underlying iterator without offset and add the offset when dereferencing the iterator. In that case your underlying iterator would take the values, &x[0], &x[2], and &x[4] - a valid one-passed-the-end iterator that can be compared to the end slice iterator. So relating to your example I would write something like: std::for_each( slice_iterator<int*,2,1>(boost::begin(x)), slice_iterator<int*,2,1>(boost::end(x)), do_stuff); and that works fine (as long as size of x is a multiple of the stride. An interesting consequence of this approach is that for a slice iterator with a run-time specified stride and offset, the end slice iterator does _not_ depend on its stride or offset. I have made this an explicit feature of a slice iterator I once wrote and found this to be very convenient as I always ended up iterating n times over a range for a stride of n (each time with a different offset). Sam Saariste

1 0

Serialization errors galore
by Victor A. Wagner Jr. 04 Jun '05

04 Jun '05

C:\Projects\boost\boost/archive/basic_archive.hpp(21) : fatal error C1189: #error : "no serialization headers my precede any archive headers" Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

2 2

serialization of objects with overloaded new/delete
by Andreas Brinck 04 Jun '05

04 Jun '05

Hi, I'm working on an application where we wan't to serialize objects with overloaded operator new/delete. After reading at the library homepage that it isn't possible I decided to take a look at the library code and found the following code snippet in iserializer.hpp: template<class T> struct heap_allocator { #if 0 // note: this fails on msvc 7.0 and gcc 3.2 <snip> static T * invoke(){ return new_operator(has_op_new(static_cast<T *>(NULL))); } #else // while this doesn't handle operator new overload for class T static T * invoke(){ return static_cast<T *>(operator new(sizeof(T))); } #endif }; Since we're using msvc 7.1 i decided to enable the disabled code and see what happened. The code didn't compile but after fixing some trivial compile errors I ended up with the following version: template<class T> struct heap_allocator { #if defined(_MSC_VER) && (_MSC_VER >= 1310) // note: this fails on msvc 7.0 and gcc 3.2 template <class U, U x> struct test; typedef char* yes; typedef int* no; template <class U> static yes has_op_new(U*, test<void* (*)(std::size_t), &U::operator new>* = 0) {return 0;} static no has_op_new(...) {return 0;} template<class U> static void * new_operator(U); static void * new_operator(yes){ return (T::operator new)(sizeof(T)); } static void * new_operator(no){ return (operator new(sizeof(T))); } static T * invoke(){ return static_cast<T *>(new_operator(has_op_new(static_cast<T *>(NULL)))); } #else // while this doesn't handle operator new overload for class T static T * invoke(){ return static_cast<T *>(operator new(sizeof(T))); } #endif }; which at least in our project compiles, links and works just fine. I sent the change to Robert Ramey and he said he would examine it but I thought I would consult the members of this list as well. Does this work as expected or are there any hidden gotchas? Regards /Andreas Brinck ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/

2 1

Re: [Boost-testing] [Type Traits] AIX 5.1/vacpp6: is_enum fails to compile (Was: documentation on performing regression tests ?)
by Toon Knapen 04 Jun '05

04 Jun '05

John Maddock <john(a)johnmaddock.co.uk> wrote: >> John, do you have any ideas what's up here? > >Not really. However there was one change to is_enum since the last >release > (http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/type_traits/is_enum .hpp?r1=1.12&r2=1.13) >and does affect the code that produces the error. So you could try >reverting the code and see if that fixes things for vacpp. OK, thanks I will try that. So if I understand correctly, the process_jam_log program does not compile as it should because it uses the type_traits? >Failing that, >the standard advice is to build the regression test helper programs with >gcc, irrespective of what compiler you're going to test on the actual test >run. Well getting gcc to run correctly on aix is probably even more difficult;-(

1 0

[Type Traits] AIX 5.1/vacpp6: is_enum fails to compile (Was: documentation on performing regression tests ?)
by Aleksey Gurtovoy 04 Jun '05

04 Jun '05

Vincent Jamart writes: >> > When I lauch the tests on AIX 5.1 (vacpp6) with: >> > python ./regression.py --runner=FFT-vacpp_6 --toolset=vacpp >> > >> > I then have these messages that I'm investigating the cause: [...] > # Building "process_jam_log" (/home/qa/cvsboost/boost/tools/build/jam_src/bin.aix/bjam "-sBOOST_BUILD_PATH=/home/qa/cvsboost:/home/qa/cvsboost/boost/tools/build/v1" "-sBOOST_ROOT=/home/qa/cvsboost/boost" "-sTOOLS=vacpp")... > "/home/qa/cvsboost/boost/boost/type_traits/is_enum.hpp", line 95.33: 1540-0063 (S) The text "<" is unexpected. > "/home/qa/cvsboost/boost/boost/type_traits/is_enum.hpp", line 147.41: 1540-0700 (I) The previous message was produced while processing "struct boost::detail::is_enum_helper<0>::type<const std::basic_string<char,std::char_traits<char>,std::allocator<char> > >". > "/home/qa/cvsboost/boost/boost/type_traits/is_enum.hpp", line 160.40: 1540-1269 (S) The template argument for the non-type template parameter of type "bool" must be an integral constant expression. John, do you have any ideas what's up here? -- Aleksey Gurtovoy MetaCommunications Engineering

2 1

Boost regression notification
by Douglas Gregor 03 Jun '05

03 Jun '05

Boost regression test failures ------------------------------ Report time: 2005-06-03T22:18:21Z Purpose: You are receiving this report because one of the libraries you maintain has regression test failures that are not accounted for. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/issues… 795 failures in 17 libraries: date_time (23) filesystem (1) iostreams (28) iterator (1) multi_index (57) numeric/interval (7) parameter (4) program_options (21) python (2) random (2) range (1) regex (6) serialization (609) spirit (3) test (23) thread (4) wave (3) |date_time| testlocal_time: vc-8_0 testlocal_time_input_facet: vc-8_0 testtime_input_facet: vc-8_0 testtime_serialize: gcc-3.3.5-linux gcc-3_3-darwin mingw-3_4_2 vc-7_1 vc-8_0 testtime_serialize_std_config: gcc-3.3.5-linux gcc-3_3-darwin mingw-3_4_2 vc-7_1 vc-8_0 testtime_serialize_xml: gcc-3.3.5-linux gcc-3_3-darwin mingw-3_4_2 vc-7_1 vc-8_0 testtime_serialize_xml_std_config: gcc-3.3.5-linux gcc-3_3-darwin mingw-3_4_2 vc-7_1 vc-8_0 |filesystem| operations_test: cw-9_5-darwin |iostreams| bzip2_test: cw-9_4 cw-9_4 code_converter_test: gcc-2.95.3-stlport-4.5.3-linux finite_state_filter_test: cw-8_3 cw-9_5-darwin vc7 gzip_test: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-stlport-4.5.3-linux gcc-3.3.5-linux gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux intel-8.1-linux msvc mapped_file_test: cw-8_3 zlib_test: cw-9_4 cw-9_4 cw-9_5-darwin gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux gcc-3.3.5-linux gcc-3.4.3-linux gcc-3_3-darwin gcc-4.0.0-linux intel-8.1-linux msvc |iterator| filter_iterator_test: borland-5_6_4 |multi_index| test_basic: msvc msvc-stlport vc7 test_capacity: msvc msvc-stlport vc7 test_comparison: msvc msvc-stlport vc7 test_composite_key: msvc msvc-stlport vc7 test_conv_iterators: msvc msvc-stlport vc7 test_copy_assignment: msvc msvc-stlport vc7 test_hash_ops: msvc msvc-stlport vc7 test_iterators: msvc msvc-stlport vc7 test_list_ops: msvc msvc-stlport vc7 test_modifiers: msvc msvc-stlport vc7 test_mpl_ops: msvc msvc-stlport vc7 test_observers: msvc msvc-stlport vc7 test_projection: msvc msvc-stlport vc7 test_range: msvc msvc-stlport vc7 test_safe_mode: msvc msvc-stlport vc7 test_set_ops: msvc msvc-stlport vc7 test_special_list_ops: msvc msvc-stlport vc7 test_special_set_ops: msvc msvc-stlport vc7 test_update: msvc msvc-stlport vc7 |numeric/interval| det: cw-9_5-darwin integer: cw-9_5-darwin mul: cw-9_5-darwin overflow: cw-9_5-darwin pi: cw-9_5-darwin pow: cw-9_5-darwin test_float: cw-9_5-darwin |parameter| basics: borland-5_6_4 macros: borland-5_6_4 sfinae: borland-5_6_4 vc-7_1 |program_options| cmdline_test: borland-5_6_4 vc7 cmdline_test_dll: borland-5_6_4 vc7 parsers_test: borland-5_6_4 intel-8.1-linux vc7 parsers_test_dll: borland-5_6_4 intel-8.1-linux vc7 positional_options_test: borland-5_6_4 positional_options_test_dll: borland-5_6_4 unicode_test: vc7 unicode_test_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_3-darwin vc7 variable_map_test: borland-5_6_4 vc7 variable_map_test_dll: borland-5_6_4 vc7 |python| numpy: gcc-3.3.5-linux vector_indexing_suite: msvc-stlport |random| random_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux |range| mfc: gcc-3.3.5-linux |regex| bad_expression_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux captures_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux recursion_test: gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux |serialization| test_array_binary_archive_dll: msvc vc7 test_array_text_archive_dll: cw-9_5-darwin msvc vc7 test_array_text_warchive_dll: cw-9_5-darwin msvc vc7 test_array_xml_archive_dll: cw-9_5-darwin msvc vc7 test_array_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_binary_binary_archive_dll: msvc vc7 test_binary_text_archive_dll: cw-9_5-darwin msvc vc7 test_binary_text_warchive_dll: cw-9_5-darwin msvc vc7 test_binary_xml_archive_dll: cw-9_5-darwin msvc vc7 test_binary_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_class_info_load_binary_archive: cw-9_4 gcc-3.3.5-linux test_class_info_load_binary_archive_dll: cw-9_4 gcc-3.3.5-linux msvc vc7 test_class_info_load_text_archive: cw-9_4 gcc-3.3.5-linux test_class_info_load_text_archive_dll: cw-9_4 gcc-3.3.5-linux msvc vc7 test_class_info_load_text_warchive: cw-9_4 gcc-3.3.5-linux test_class_info_load_text_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux msvc vc7 test_class_info_load_xml_archive: cw-9_4 gcc-3.3.5-linux test_class_info_load_xml_archive_dll: cw-9_4 gcc-3.3.5-linux msvc vc7 test_class_info_load_xml_warchive: cw-9_4 gcc-3.3.5-linux test_class_info_load_xml_warchive_dll: cw-9_4 cw-9_5-darwin gcc-3.3.5-linux msvc vc7 test_class_info_save_binary_archive_dll: msvc vc7 test_class_info_save_text_archive_dll: cw-9_5-darwin msvc vc7 test_class_info_save_text_warchive_dll: cw-9_5-darwin msvc vc7 test_class_info_save_xml_archive_dll: msvc vc7 test_class_info_save_xml_warchive_dll: cw-9_5-darwin msvc vc7 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 msvc-stlport vc7 test_const_save_fail2: msvc msvc-stlport vc7 test_const_save_fail3: msvc msvc-stlport vc7 test_contained_class_binary_archive_dll: msvc vc7 test_contained_class_text_archive_dll: cw-9_5-darwin msvc vc7 test_contained_class_text_warchive_dll: cw-9_5-darwin msvc vc7 test_contained_class_xml_archive_dll: cw-9_5-darwin msvc vc7 test_contained_class_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_cyclic_ptrs_binary_archive_dll: msvc vc7 test_cyclic_ptrs_text_archive_dll: cw-9_5-darwin msvc vc7 test_cyclic_ptrs_text_warchive_dll: cw-9_5-darwin msvc vc7 test_cyclic_ptrs_xml_archive_dll: cw-9_5-darwin msvc vc7 test_cyclic_ptrs_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_delete_pointer_binary_archive_dll: msvc vc7 test_delete_pointer_text_archive_dll: cw-9_5-darwin msvc vc7 test_delete_pointer_text_warchive_dll: cw-9_5-darwin msvc vc7 test_delete_pointer_xml_archive_dll: cw-9_5-darwin msvc vc7 test_delete_pointer_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_demo_auto_ptr_dll: cw-9_5-darwin msvc vc7 test_demo_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_exception_dll: cw-9_4 cw-9_4 cw-9_5-darwin test_demo_fast_archive_dll: msvc vc7 test_demo_pimpl_dll: cw-9_5-darwin msvc vc7 test_demo_polymorphic_dll: cw-9_5-darwin msvc vc7 test_demo_portable_archive: cw-9_5-darwin gcc-3_3-darwin gcc-3_3-darwin test_demo_portable_archive_dll: cw-9_5-darwin gcc-3_3-darwin gcc-3_3-darwin 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 vc7 test_demo_xml_dll: msvc vc7 test_deque_binary_archive_dll: msvc vc7 test_deque_text_archive_dll: cw-9_5-darwin msvc vc7 test_deque_text_warchive_dll: cw-9_5-darwin msvc vc7 test_deque_xml_archive_dll: cw-9_5-darwin msvc vc7 test_deque_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_binary_archive_dll: msvc vc7 test_derived_class_binary_archive_dll: msvc vc7 test_derived_class_ptr_binary_archive_dll: msvc vc7 test_derived_class_ptr_text_archive_dll: cw-9_5-darwin msvc vc7 test_derived_class_ptr_text_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_class_ptr_xml_archive_dll: cw-9_5-darwin msvc vc7 test_derived_class_ptr_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_class_text_archive_dll: cw-9_5-darwin msvc vc7 test_derived_class_text_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_class_xml_archive_dll: cw-9_5-darwin msvc vc7 test_derived_class_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_text_archive_dll: cw-9_5-darwin msvc vc7 test_derived_text_warchive_dll: cw-9_5-darwin msvc vc7 test_derived_xml_archive_dll: msvc vc7 test_derived_xml_warchive_dll: cw-9_5-darwin msvc vc7 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_exported_binary_archive_dll: msvc vc7 test_exported_text_archive_dll: msvc vc7 test_exported_text_warchive_dll: msvc vc7 test_exported_xml_archive_dll: msvc vc7 test_exported_xml_warchive_dll: msvc vc7 test_list_binary_archive_dll: msvc vc7 test_list_ptrs_binary_archive_dll: msvc vc7 test_list_ptrs_text_archive_dll: cw-9_5-darwin msvc vc7 test_list_ptrs_text_warchive_dll: cw-9_5-darwin msvc vc7 test_list_ptrs_xml_archive_dll: cw-9_5-darwin msvc vc7 test_list_ptrs_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_list_text_archive_dll: cw-9_5-darwin msvc vc7 test_list_text_warchive_dll: cw-9_5-darwin msvc vc7 test_list_xml_archive_dll: cw-9_5-darwin msvc vc7 test_list_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_map_binary_archive_dll: msvc vc7 test_map_text_archive_dll: cw-9_5-darwin msvc vc7 test_map_text_warchive_dll: cw-9_5-darwin msvc vc7 test_map_xml_archive_dll: cw-9_5-darwin msvc vc7 test_map_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_mi_binary_archive_dll: vc7 test_mi_text_archive_dll: vc7 test_mi_text_warchive_dll: vc7 test_mi_xml_archive_dll: vc7 test_mi_xml_warchive_dll: vc7 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 vc7 test_multiple_ptrs_binary_archive_dll: msvc vc7 test_multiple_ptrs_text_archive_dll: cw-9_5-darwin msvc vc7 test_multiple_ptrs_text_warchive_dll: cw-9_5-darwin msvc vc7 test_multiple_ptrs_xml_archive_dll: cw-9_5-darwin msvc vc7 test_multiple_ptrs_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_no_rtti_binary_archive_dll: msvc vc7 test_no_rtti_text_archive_dll: msvc vc7 test_no_rtti_text_warchive_dll: msvc vc7 test_no_rtti_xml_archive_dll: msvc vc7 test_no_rtti_xml_warchive_dll: msvc vc7 test_non_default_ctor2_binary_archive_dll: msvc vc7 test_non_default_ctor2_text_archive_dll: msvc vc7 test_non_default_ctor2_text_warchive_dll: msvc vc7 test_non_default_ctor2_xml_archive_dll: msvc vc7 test_non_default_ctor2_xml_warchive_dll: msvc vc7 test_non_default_ctor_binary_archive_dll: msvc vc7 test_non_default_ctor_text_archive_dll: cw-9_5-darwin msvc vc7 test_non_default_ctor_text_warchive_dll: cw-9_5-darwin msvc vc7 test_non_default_ctor_xml_archive_dll: cw-9_5-darwin msvc vc7 test_non_default_ctor_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_non_intrusive_binary_archive_dll: msvc vc7 test_non_intrusive_text_archive_dll: cw-9_5-darwin msvc vc7 test_non_intrusive_text_warchive_dll: cw-9_5-darwin msvc vc7 test_non_intrusive_xml_archive_dll: cw-9_5-darwin msvc vc7 test_non_intrusive_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_null_ptr_binary_archive_dll: msvc vc7 test_null_ptr_text_archive_dll: cw-9_5-darwin msvc vc7 test_null_ptr_text_warchive_dll: cw-9_5-darwin msvc vc7 test_null_ptr_xml_archive_dll: msvc vc7 test_null_ptr_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_nvp_binary_archive_dll: msvc vc7 test_nvp_text_archive_dll: cw-9_5-darwin msvc vc7 test_nvp_text_warchive_dll: cw-9_5-darwin msvc vc7 test_nvp_xml_archive_dll: cw-9_5-darwin msvc vc7 test_nvp_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_object_binary_archive_dll: msvc vc7 test_object_text_archive_dll: msvc vc7 test_object_text_warchive_dll: cw-9_5-darwin msvc vc7 test_object_xml_archive_dll: msvc vc7 test_object_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_optional_binary_archive_dll: msvc vc7 test_optional_text_archive_dll: cw-9_5-darwin msvc vc7 test_optional_text_warchive_dll: cw-9_5-darwin msvc vc7 test_optional_xml_archive_dll: cw-9_5-darwin msvc vc7 test_optional_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_polymorphic_binary_archive_dll: msvc vc7 test_polymorphic_text_archive_dll: cw-9_5-darwin msvc vc7 test_polymorphic_text_warchive_dll: cw-9_5-darwin msvc vc7 test_polymorphic_xml_archive_dll: cw-9_5-darwin msvc vc7 test_polymorphic_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_primitive_binary_archive: mingw-3_4_2 test_primitive_binary_archive_dll: mingw-3_4_2 msvc vc7 test_primitive_text_archive: mingw-3_4_2 test_primitive_text_archive_dll: mingw-3_4_2 msvc vc7 test_primitive_text_warchive_dll: cw-9_5-darwin msvc vc7 test_primitive_xml_archive: mingw-3_4_2 test_primitive_xml_archive_dll: mingw-3_4_2 msvc vc7 test_primitive_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_private_ctor_dll: cw-9_5-darwin msvc vc7 test_recursion_binary_archive_dll: msvc vc7 test_recursion_text_archive_dll: cw-9_5-darwin msvc vc7 test_recursion_text_warchive_dll: cw-9_5-darwin msvc vc7 test_recursion_xml_archive_dll: cw-9_5-darwin msvc vc7 test_recursion_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_registered_binary_archive_dll: msvc vc7 test_registered_text_archive_dll: msvc vc7 test_registered_text_warchive_dll: msvc vc7 test_registered_xml_archive_dll: msvc vc7 test_registered_xml_warchive_dll: msvc vc7 test_reset_object_address_dll: cw-9_5-darwin vc7 test_set_binary_archive_dll: msvc vc7 test_set_text_archive_dll: cw-9_5-darwin msvc vc7 test_set_text_warchive_dll: cw-9_5-darwin msvc vc7 test_set_xml_archive_dll: cw-9_5-darwin msvc vc7 test_set_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_shared_ptr_binary_archive: borland-5_6_4 msvc vc7 test_shared_ptr_binary_archive_dll: borland-5_6_4 msvc vc7 test_shared_ptr_text_archive: borland-5_6_4 msvc vc7 test_shared_ptr_text_archive_dll: borland-5_6_4 msvc vc7 test_shared_ptr_text_warchive: borland-5_6_4 msvc vc7 test_shared_ptr_text_warchive_dll: borland-5_6_4 msvc vc7 test_shared_ptr_xml_archive: borland-5_6_4 msvc vc7 test_shared_ptr_xml_archive_dll: borland-5_6_4 msvc vc7 test_shared_ptr_xml_warchive: borland-5_6_4 msvc vc7 test_shared_ptr_xml_warchive_dll: borland-5_6_4 msvc vc7 test_simple_class_binary_archive_dll: msvc vc7 test_simple_class_ptr_binary_archive_dll: msvc vc7 test_simple_class_ptr_text_archive_dll: cw-9_5-darwin msvc vc7 test_simple_class_ptr_text_warchive_dll: cw-9_5-darwin msvc vc7 test_simple_class_ptr_xml_archive_dll: cw-9_5-darwin msvc vc7 test_simple_class_ptr_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_simple_class_text_archive_dll: cw-9_5-darwin msvc vc7 test_simple_class_text_warchive_dll: cw-9_5-darwin msvc vc7 test_simple_class_xml_archive_dll: cw-9_5-darwin msvc vc7 test_simple_class_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_split_binary_archive_dll: msvc vc7 test_split_text_archive_dll: cw-9_5-darwin msvc vc7 test_split_text_warchive_dll: cw-9_5-darwin msvc vc7 test_split_xml_archive_dll: msvc vc7 test_split_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_tracking_binary_archive_dll: msvc vc7 test_tracking_text_archive_dll: cw-9_5-darwin msvc vc7 test_tracking_text_warchive_dll: cw-9_5-darwin msvc vc7 test_tracking_xml_archive_dll: msvc vc7 test_tracking_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_unregistered_binary_archive_dll: msvc vc7 test_unregistered_text_archive_dll: msvc vc7 test_unregistered_text_warchive_dll: msvc vc7 test_unregistered_xml_archive_dll: msvc vc7 test_unregistered_xml_warchive_dll: msvc vc7 test_variant_binary_archive_dll: msvc vc7 test_variant_text_archive_dll: cw-9_5-darwin msvc vc7 test_variant_text_warchive_dll: cw-9_5-darwin msvc vc7 test_variant_xml_archive_dll: cw-9_5-darwin msvc vc7 test_variant_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_vector_binary_archive_dll: msvc vc7 test_vector_text_archive_dll: cw-9_5-darwin msvc vc7 test_vector_text_warchive_dll: cw-9_5-darwin msvc vc7 test_vector_xml_archive_dll: cw-9_5-darwin msvc vc7 test_vector_xml_warchive_dll: cw-9_5-darwin msvc vc7 test_void_cast_dll: vc7 |spirit| bug_fixes: cw-9_5-darwin bug_fixes_debug: cw-9_5-darwin owi_mt_tests: gcc-3_3-darwin |test| boost_check_equal_str: borland-5_6_4 errors_handling_test: cw-9_5-darwin vc-8_0 ifstream_line_iterator_test: gcc-3.4.3-linux gcc-4.0.0-linux mingw-3_4_2 test_fp_comparisons: borland-5_6_4 msvc msvc-stlport vc7 test_tools_test: cw-9_4 cw-9_4 cw-9_5-darwin token_iterator_test: borland-5_6_4 cw-8_3 cw-9_4 cw-9_4 gcc-2.95.3-linux gcc-2.95.3-stlport-4.5.3-linux gcc-4.0.0-linux vc7 wide_string: vc-7_1 vc-8_0 |thread| test_read_write_mutex: borland-5_6_4 test_thread_lib: cw-8_3 test_tss_lib: cw-9_4 cw-9_4 |wave| test_slex_lexer: cw-9_5-darwin testwave: cw-8_3 cw-9_5-darwin

1 0

Keeping track of library maintainers
by Doug Gregor 03 Jun '05

03 Jun '05

It isn't always obvious who maintains a given library. The authors listed in the documentation have often come and gone, and now someone else handles it. So, I've started the file libs/maintainers.txt, which I hope we can keep up-to-date with the maintainers for each library. I've initialized the file with all of the libraries listed in the regression tests, and put in the maintainers that I believe are still active. Please update the list in CVS or reply with any changes that need to be made. Doug algorithm/minmax Herve Bronnimann <hbr -at- poly.edu> algorithm/string Pavol Droba <droba -at- topmail.sk> any array assign Thorsten Ottosen <nesotto -at- cs.auc.dk> bind Peter Dimov <pdimov -at- mmltd.net> concept_check config John Maddock <john -at- johnmaddock.co.uk> conversion crc date_time Jeff Garland <jeff -at- crystalclearsoftware.com> disjoint_sets dynamic_bitset filesystem Beman Dawes <bdawes -at- acm.org> format function Douglas Gregor <dgregor -at- cs.indiana.edu> functional functional/hash Daniel James <daniel -at- calamity.org.uk> graph Douglas Gregor <dgregor -at- cs.indiana.edu> integer io iostreams Jonathan Turkanis <technews -at- kangaroologic.com> iterator David Abrahams <dave -at- boost-consulting.com>, Thomas Witt <witt - at - acm.org> lambda Jaakko Jarvi <jarvi -at- cs.tamu.edu> logic Douglas Gregor <dgregor -at- cs.indiana.edu> math Hubert Holin <Hubert.Holin -at- meteo.fr> mpl Aleksey Gurtovoy <agurtovoy -at- meta-comm.com>, David Abrahams <dave -at- boost-consulting.com> multi_array Ronald Garcia <garcia -at- osl.iu.edu> multi_index Joaquin M Lopez Munoz <joaquin -at- tid.es> numeric/conversion Fernando Cacciola <fernando_cacciola -at- ciudad.com.ar> numeric/interval Sylvain Pion <Sylvain.Pion -at- sophia.inria.fr>, Herve Bronnimann <hbr -at- poly.edu>, Guillaume Melquiond <guillaume.melquiond -at- ens-lyon.fr> numeric/ublas optional Fernando Cacciola <fernando_cacciola -at- ciudad.com.ar> parameter David Abrahams <dave -at- boost-consulting.com>, Daniel Wallin <dalwan01 -at- student.umu.se> pool preprocessor program_options Vladimir Prus <ghost -at- cs.msu.su> property_map Douglas Gregor <dgregor -at- cs.indiana.edu> ptr_container Thorsten Ottosen <nesotto -at- cs.auc.dk> python David Abrahams <dave -at- boost-consulting.com> random range Thorsten Ottosen <nesotto -at- cs.auc.dk> rational regex John Maddock <john -at- johnmaddock.co.uk> serialization Robert Ramey <ramey -at- rrsd.com> signals Douglas Gregor <dgregor -at- cs.indiana.edu> smart_ptr Beman Dawes <bdawes -at- acm.org>, Peter Dimov <pdimov -at- mmltd.net> spirit Joel de Guzman <djowel -at- gmail.com> static_assert John Maddock <john -at- johnmaddock.co.uk> test Gennadiy Rozental <gennadiy.rozental -at- thomson.com> thread Michael Glassford <glassfordm -at- hotmail.com> timer Beman Dawes <bdawes -at- acm.org> tokenizer tuple Jaakko Jarvi <jarvi -at- cs.tamu.edu> type_traits John Maddock <john -at- johnmaddock.co.uk>, David Abrahams <dave -at- boost-consulting.com> utility variant wave Hartmut Kaiser <hartmut.kaiser -at- gmail.com>

1 0

Customer Friendlier Boost Installation
by Paul A Bristow 03 Jun '05

03 Jun '05

Recently we had a flurry of discussion of why Boost is not more widely used. I have used some bits of Boost happily for years, but recently I felt I had to use it 'properly' so concluded it was time I used the bjam build system - something I had felt looked a bit clever. Indeed my suspicion was proved correct - I couldn't get it to work. The instructions are far too Unix/Make oriented for this mere Windows hacker; the Wiki Windows specific instructions are much better but suggest copying (duplicating) a lot of files to avoid an addition to the include directories, and don't apply to the most recent compilers. Victor Wagner gave some hints recently using environment variables, but not the full text. I don't doubt the usefulness of the bjam to the congescenti - only with this could the incredibly impressive build & test system allow all the cracks and chasms of compiler non-compliance and language imprecision to be papered over - Boost's great strength. But if we are to interest your average Windows IDE programmer, for whom MAKE is a blank or a distant nightmare, IMO we need some much better and simpler instructions, including lots of examples of input and output, and to be as well tested as the rest of Boost code. Like it or not, these are the potential customers and I spoken to many who are put off by the 'build barrier'. I suggest that we explicitly say that you can use all of Boost (except the ones that must have built libraries) by adding to the include list - and say exactly how in Windows IDE-ese. If you share my concern, would some someone like to prepare something? Or at least provide details of their way of doing it. I will be willing to help with checking/editing. Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow(a)hetp.u-net.com

33 194

RE: [boost] Re: Typeof: Review result
by Powell, Gary 03 Jun '05

03 Jun '05

>Meanwhile I am very much puzzled with the inconsistency of rather high >download activity and relatively low amount of feedback the Typeof library >has received on the list. If somebody could offer a reasonable explanation >of this fact, it would help us a lot in our future work with boost. >Best regards, >Arkadiy I suspect its because while a "Typeof" library is very useful, its tedious code to understand. And that's coming from someone who wrote one, with help from Jaakko Jarvi.. (lambda) And I too had intended to at least take a look at this library with the future intent on dropping the internal version in lambda, as I'm sure Joel is too for spirit. However at this time in my life no amount of delay would have helped unless we are talking about 2008.. when I should again have a quieter life. However I will try and give it a once over knowing that any comments are well past the due date. IMO if there are 3 decent reviews then that is probably enough. Still though its a sad state of the world's affairs with a list in the low thousands of users we can't muster more than 3 people with enough time to look at something new and cool. Yours, -Gary-

1 0

yield statement proposal
by Maksym Motornyy 03 Jun '05

03 Jun '05

Hi all, As of version 2.0 C# will have yield statement. It intended for simplifying iterator development. Yield suspends execution of iterator code and resumes it on next increment. Thus complex traversal iterators are much easier to write in natural loop-like form instead of unroll them. Consider following example (C#): public IEnumerator< int > GetEnumerator() { for ( int i = 1; i < 4; ++i ) for ( int j = 1; j < 4; ++i ) yield return i * j; } Such iterator will generate following sequence: 1 2 3 2 4 6 3 6 9. The same code in C++ (using my library) will look like: class simple_generator { public: YIELD_BEGIN_WITH_CTOR( simple_generator, int ) YIELD_FOR_0( i = 1, i < 4, ++i ) YIELD_FOR_1( j = 1, j < 4, ++j ) YIELD_RETURN( i * j ) YIELD_END_FOR_1 YIELD_END_FOR_0 YIELD_END private: int i; int j; }; int main( int, char ** ) { for ( simple_generator g; !g.at_end(); ++g ) cout << *g << " "; return 0; } Have a look at few more examples: Example 1: YIELD_BEGIN_WITH_CTOR( simple_generator, string ) YIELD_RETURN( "Hello," ) YIELD_RETURN( "world!" ) YIELD_END Will print "Hello, world!" in two iterations with the above main() function. Example 2: YIELD_BEGIN_WITH_CTOR( simple_generator, int ) YIELD_FOR( i = 0, i < 10, ++i ) YIELD_IF( i % 2 == 0 ) YIELD_CONTINUE YIELD_END_IF YIELD_RETURN( i ) YIELD_END_FOR YIELD_END Will print "1 3 5 7 9 ". If anyone interested in such thing? Sincerely yours, Maksym Motornyy.

7 12

An interpreter: useful proposal?
by Daniel Gutson 03 Jun '05

03 Jun '05

Hi there, I'm developing an interpreter library support for a project, and I was wondering whether this could be of any help out there. Would it be useful? It provides some structured basic facilities, such as variables, l- and r-values, expressions, functions, subroutines, nested statements, but no object orientation yet. Please let me know whether it's worth the effort to share it here! (since there's still some work to be done :) ). Rgds, Daniel.

1 0

[date_time] CW-9 failures.
by Rene Rivera 03 Jun '05

03 Jun '05

There are some failures for date_time with CW-9 (and similar errors in CW-8): CW-9.5 on Mac... http://tinyurl.com/bwhsw http://tinyurl.com/93nh4 CW-9.4 on Windows... http://tinyurl.com/75t78 http://tinyurl.com/br2b5 CW-8.3 on Windows... http://tinyurl.com/85nf5 http://tinyurl.com/9gfpn They have this as the reason: "[ J. Garland ] Some older compilers are confused by the template code here. These are new features to date-time in 1.33 and there is no plan to backport to these non-compliant compilers." Now I don't particularly think of CW-9 as an "older" compiler. So is that really the reason? Or is it just that it hasn't been investigated? -- -- 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

3 3

RE: [boost] Re: yield statement proposal
by Marcin Tustin 03 Jun '05

03 Jun '05

> -----Original Message----- > From: Giovanni P. Deretta [mailto:gpderetta@gmail.com] > Sent: 03 June 2005 03:15 > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: yield statement proposal > Speaking of more Boost centric stuff? There has been any > proposal of a coroutine library? I think it should definitely > be useful and not really that hard to implement (fibers on > windows and makecontext or the setjump/sigaltstack trick on > unices). Anyone interested? What about a continuation library? Then co-routines could simply be built on top of that, along with everything else that can be built on top of continuations.

2 1

Template argument deduction question
by Vladimir Prus 03 Jun '05

03 Jun '05

Hello, the program_options library fails one tests on EDG compilers (Intel, Como), which a failure to deduce template arguments for a certain call. After reading the standard for some time, I failed to understand the reason. Below is the test program: char* cmdline3_[1] = {}; template<class charT> void func(const charT* const argv[]) {} int main() { // P is 'const charT* const argv[]'cmdline3_ // A is 'char* cmdline3_[]' // // According to 14.8.2.1/2 // If P is not reference type // -If A is an array type, the pointer type produced // by the array-to-pointer standard convertion (4.2) // is used in place of A for type deduction. // // So, A should become 'char**' // The following does not compile. func(cmdline3_); char** p = cmdline3_; // This does compile, even though the argument type used for // type deduction should be the same as in example above. func(p); } Anybody can explain what's going on? TIA, Volodya

3 4

Probing interest in fixed dimension matrix class
by christopher diggins 03 Jun '05

03 Jun '05

I have just finished writing a fixed dimensionality matrix template (kmatrix<T, Rows, Cols>) which appears to significantly outperform the ublas::matrix. Is there any interest? Below are the results of the benchmarks using Visual C++ 7.1 on an Intel Celeron 1.6 GHZ: Integer matrix multiplication: 2,2 X 2,2 kmatrix 94 msec elapsed ublas 578 msec elapsed 3,3 X 3,3 kmatrix 250 msec elapsed ublas 891 msec elapsed 100,100 X 100,100 kmatrix 593 msec elapsed ublas 1422 msec elapsed 100,1 X 1,100 kmatrix 172 msec elapsed ublas 266 msec elapsed 1,100 X 100,1 kmatrix 625 msec elapsed ublas 1718 msec elapsed Double matrix multiplication: 2,2 X 2,2 kmatrix 94 msec elapsed ublas 593 msec elapsed 3,3 X 3,3 kmatrix 297 msec elapsed ublas 1235 msec elapsed 100,100 X 100,100 kmatrix 766 msec elapsed ublas 1625 msec elapsed 100,1 X 1,100 kmatrix 203 msec elapsed ublas 328 msec elapsed 1,100 X 100, 1 kmatrix 813 msec elapsed ublas 2125 msec elapsed Christopher Diggins http://www.cdiggins.com

8 16

[filesystem] Generic path grammar corner cases
by Beman Dawes 03 Jun '05

03 Jun '05

I'm working to align the Boost.Filesystem generic path grammar with the POSIX specification. Doing so clarifies the specification of the library, and ensures that all native paths for both POSIX and Windows will work correctly. (Windows follows the POSIX conventions in some of the corner cases involved.) The particular cases involve extra slashes in paths. For example, "/foo//bar//". I was surprised to find that such a path is well-defined for POSIX and Windows, with a meaning of "/foo/bar/." In other words, multiple slashes treated as a single slash, and paths with a trailing slash treated as if a period was appended. The rules for more than two leading slashes are a bit more complex - for POSIX they are treated as a single slash, for Windows that is an invalid path. Question: what should path("foo//bar//").string() yield? 1) "foo//bar//" 2) "foo/bar/" 3) "foo/bar/." (1) follows the rule that the path string is always exactly as input. Desirable in that if a platform actually implements something a bit different from the POSIX specs for multiple slashes, implementations will behave as expected for the platform. Downside is much more complex implementation (because many more functions have to be able to cope with multiple slashes) and more complex testing. (2) Desirable in that if a platform actually implements something a bit different from the POSIX (and Windows) specs for multiple slashes, implementations will behave portably and correctly in a POSIX (and Windows) sense. (3) Desirable in that for all three options directory iteration will return three elements - "foo", "bar", "." - so it is a bit counter intuitive for the "." not to appear in the string() results. Not a strong argument. I'm leaning toward (2). Any comments? --Beman

7 12

fusion::for_each question: Why const operator in the fctor?
by Brian Braatz 03 Jun '05

03 Jun '05

I am using the fusion code in 1.32 with the vc 71. compiler. My question is, considering the following unit test (for_each_tests.cpp) struct print { template <typename T> void operator()(T const& v) const { std::cout << "[ " << v << " ] "; } }; { typedef tuple<int, char, double, char const*> tuple_type; tuple_type t(1, 'x', 3.3, "Ruby"); for_each(t, print()); std::cout << std::endl; } (this code runs correctly for me) If I change the function to: struct print { template <typename T> void operator()(T & v) const { std::cout << "[ " << v << " ] "; } }; It still works, but changing it to struct print { template <typename T> void operator()(T & v) { std::cout << "[ " << v << " ] "; } }; Does not work. Why does the functor need to have a const operator()? I have been trying to take a tuple<> and touch each node in the tuple (ala for_each in fusion), which I was *very* happy to find fusion has this as working functionality. But, the next step for me is to have the functor write to its local member variables. I.e. requiring const here really limits the usefulness of the fusion::for_each. I look in my compilers header and noticed that stl::for_each does not have a const requirement on the functor. Is this a mistake? Is there a reason I am not seeing why for_each would have this limitation? Thanks for any help and guidance. Brian "Remember, there are no stupid questions. Only stupid people....."

2 1

RE: [boost] Re: Probing interest in fixed dimension matrix class
by Martin Bonner 03 Jun '05

03 Jun '05

----Original Message---- From: Deane Yang [mailto:deane_yang@yahoo.com] Sent: 02 June 2005 16:57 To: boost(a)lists.boost.org Subject: [boost] Re: Probing interest in fixed dimension matrix class > Andy Little wrote: >> >> eg to find the point 1/3 rd way from the start of line(A , B) one >> could calculate 2/3 *A +1/3 * B. >> > > I think it is more natural to compute this as > > A + (1/3)*(B - A), > > where A and B are points and B - A is a vector. So you're really still > just adding a vector to a point to get a new point. There is never a > need to add or rescale points. Hmm. To me that looks a very UNnatural recasting of the original in order to satisfy the rule. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

Sunday: Mailing list outage
by David Abrahams 02 Jun '05

02 Jun '05

-- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

set arithmetic proposal
by Dominic Herity 02 Jun '05

02 Jun '05

I've often wished that STL sets supported set arithmetic operations. Addition, multiplication and subtraction operators could be overloaded with set union, intersection and difference respectively. For example: set<char> s1; // s1 <- {} s1 += 'a'; // s1 <- {a} set<char> s2 = s1 + 'b'; // s2 <- {a,b} set<char> s3 = s2 - s1; // s3 <- {b} set<char> s4 = s1 * s2; // s4 <- {a} Achieving the above results with the existing STL library is by comparison cumbersome, error-prone and unclear. Although this proposal does not follow the STL design philosophy, it meets a real developer need. It can be implemented using global operator overloads, which should avoid conflicts with other uses of STL sets. Comments and suggestions welcome. Best Regards Dominic Herity Red Plain Technology (www.redplain.com) T:+353-87-2208233 F: +1-603-909 6570 E: dominic.herity(a)redplain.com

6 7

Re: Typeof: Review result
by Tom Brinkman 02 Jun '05

02 Jun '05

>> >> I am pleased to formally announce that the Typeof library has been accepted into >> Boost. > > Congratulations Arkadiy and Peder. > >> There were 3 reviews, all in favour of accepting the library. > > While I'm not questioning the value of accepting this library > specifically, doesn't it seem less than ideal to accept a library > that -- for whatever reasons -- garnered only three reviews? >> Yes. > While the library was truly peer reviewed, and the reviews were > by knowledgeable folk, the base of input is narrow as a result. > Should this be the norm? >> No. Not sure what we can do about it. I think the review wizard > should weigh in here. Three positive reviews is not sufficient in my opinion. However, the precedent has already be set, as other libraries have been approved on a similar limited number of reviews. I'm sure most would agree that the review situation is not ideal and could be improved. However, it has worked to some extent and the boost c++ libraries, are arguably among the best available. One easy improvement would be to require that each approved library be endorsed/sponsered by a least one prominent boost member, such as Dave Abrahms, Jeff Garland or Thorsten Ottosen. Another easy improvement would be to add accepted libraries under a probation or beta period of say six months. The library would remain beta until its stable enough and has additional time for more user scrutiny. A prominent boost member would make the judgement about when to remove the library from its beta period. During the beta period, the library author would be asked to complete the libraries documentation, examples and requested changes from the additional user scrutiny. If there are no objections, I will start requesting that libraries under review be sponsered by at least prominent boost member. This would ensure that accepted libraries meet the approval of a least one prominent boost member. Review Wizard, Tom Brinkiman

11 14

Boost/SourceForge statistics
by Beman Dawes 02 Jun '05

02 Jun '05

SourceForge has markedly improved project statistics reporting. See http://sourceforge.net/project/stats/index.php?group_id=7586&ugn=boost I found the pages viewed numbers interesting. Looks like www.boost.org has been serving an average of about 22,000 page views a day in recent months. I suppose some sites serve up that many pages in a minute or a second, but 22,000/day doesn't seem too bad for a C++ library effort. --Beman

2 1

Pointers to member function templates as template arguments
by Jonathan Turkanis 02 Jun '05

02 Jun '05

Hi, Consider the following code: template<typename T, void (T::*) (int)> struct MemFn; struct Foo { template<typename Int> void bar(Int) { } }; typedef MemFn<Foo, &Foo::bar> type; This compiles with VC7.1, GCC 3.4, Intel 8.0 and Comeau 4.3.3 in strict mode, but CodeWarrior 9.4 fails with the message: Error : illegal implicit member pointer conversion example.cpp line 9 typedef MemFn<Foo, &Foo::bar> type; Looking at 14.3.2/1, I notice while the third bullet, on function pointers, explicitly mentions templates, the fourth bullet, on pointers to members, doesn't. But perhaps pointers to function templates are covered implicitly. Looking at 14.3.2/5, bullet 6, I see that no conversions are applied to pointers to members. But no conversions are needed in the above example. What's needed is overload resolution, which is explicitly allowed. So who's right -- Metrowerks or everyone else? Jonathan

2 5

[iostreams] failure do build zlib.cpp in cvs HEAD
by pedro.lamarao＠mndfck.org 02 Jun '05

02 Jun '05

It seems the declaration of zlib_base::reset in zlib.hpp doesn't agree with the definition in zlib.cpp. After applying the following trivial patch everything compiles fine. -- Pedro Lamarão Index: boost/iostreams/filter/zlib.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/iostreams/filter/zlib.hpp,v retrieving revision 1.18 diff -r1.18 zlib.hpp 194c194 < void reset(bool compress); --- > void reset(bool compress, bool realloc);

2 1

PyQt and Boost.Python working together
by thor.arne.johansen＠ibas.no 02 Jun '05

02 Jun '05

I found a long thread discussing this topic, but the conclusion escaped me... Is it possible to use an extension created with BPL in a program using PyQt to provide a GUI? -- Thor Arne Johansen Technical Director Ibas AS

2 1

[Boost-bugs] [ boost-Support Requests-1213620 ] Configure options (CCFLAGS, LDFLAGS) ignored in build ?
by SourceForge.net 02 Jun '05

02 Jun '05

Support Requests item #1213620, was opened at 2005-06-02 09:27 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=1213620&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Configure options (CCFLAGS, LDFLAGS) ignored in build ? Initial Comment: Hi, on our Red Hat Enterprise Linux 3.0 Opteron Machine the g++ is configured to produce 64-bit binaries. When trying to build 32-bit objects via the "-m32" compiler and linker options, the boost build mechanism simply seems to ignore the option provided. Interestingly one can provide this option to the configure script but in it's output (the user.hpp file) the option only appears as a comment. It seems to get completely ignored in the subsequent build and test stages ! Is this true or am I missing some way to configure things here ? How can I supply special compile/link options to the build/test stages of the boost build process ??? Thanks in advance Frank-Oliver ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1213620&group_… ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

RE: [boost] Re: [filesystem] Generic path grammar corner cases
by Simon Li 02 Jun '05

02 Jun '05

> From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes > A fix for both issues would be to introduce an escape > sequence which means "slash and I really mean it", or an > escape path prefix which means "don't modify this path in any way." > > Both of those seem like ugly warts, and I've been avoiding > them until someone comes up with a compelling use case. I > would hate to do something ugly that may have no practical > use whatsoever. > > Hum... Gears clank in brain for awhile... > > In the past, whenever I thought about escape sequences, I > assumed we would have to invent a new escape sequence, and > that would be quite messy. But what about hijacking one of > the existing escape sequences? > > Of all the C++ escape sequences, '\a' stands for BEL, and > would seem to have the least probability of ever being a > valid character in a path. It isn't valid at all for some > OS's. If Boost.Filesystem hijacked it as an escape sequence > meaning ""slash and I really mean it", we could use option > (2) with all its advantages, yet if someone desperately needs > more slashes for whatever reason, they have a way of doing so. > > Thoughts? In the unlikely event that there is a filename with a BEL in it, is there a way of "unescaping" the \a so that it isn't converted into a slash? If anyone's wondering about BEL being a valid filename character, I've just done a quick test on Linux: [0 simon@cstux test]$ mkdir `echo -e 'foo\abar'` # The stuff with echo ensures the argument passed to mkdir is a BEL char [0 simon@cstux test]$ ls foo?bar [0 simon@cstux test]$ ls | od -a 0000000 f o o bel b a r nl 0000010 # od -e converts its raw input into ascii chars, or their equivalent Simon This e-mail message (including its attachments) is private, is intended for the recipient named in it and may contain material which is confidential and privileged. No-one other than the named recipient may read, copy, rely on, redirect, save or alter the message or any part of it or any attachment to it in any way. VMS does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not represent those of VMS unless otherwise specifically stated. While reasonable effort has been made to ensure this message is free of viruses, opening and using this message is at the risk of the recipient.

1 0

RFC: various utility classes (factory, plugin, parser iterator)
by Simon Richter 02 Jun '05

02 Jun '05

Hi, as probably everyone in here, I have written many factory implementations and plugin managers in various projects, and decided to throw them all together into a set of template classes. My current approach looks like this: - class registrable base class for objects that can be registered somewhere - class registry : public registrable base class for objects that need to register some other objects. inherits from registrable, so there can be a registry of all registries (I think that can be made optional, but haven't found a compelling reason to do so). defines a set of abstract functions that registries need to implement (register/unregister of const/non-const objects), and static functions to register/unregister objects (by going through the list of registries and passing the object to each). - template<typename obj> class creator : public registrable base class for objects responsible for instantiating a concrete class and providing an object to match the factory argument against. - template<typename obj> class factory : public registry<creator<object_type>> factory. registers creators and can be asked to instantiate objects. - template<typename obj, typename stream> class parser base class for parsers. holds a stream reference and an object of "obj" type, defines some abstract functions and knows how to create proxy objects for the postincrement operator. - template<typename obj, typename stream> class parseiterator holds and owns a pointer to a parser<obj, stream> object, behaves like an iterator. can be instantiated on the stack, uses parameters to instantiate parser by using factory<parser<obj, stream>>. I believe these things are fairly generic and was surprised that they weren't already there. Would it make sense to add these to boost (after properly specifying and documenting them, of course)? Simon

2 2

Boost.Filesystem path iterators
by Jordan DeLong 02 Jun '05

02 Jun '05

First; pre-emptive apologies if this should be sent to boost-users instead of here (or I guess the Mod can nuke it and tell me). I figured I should send it here because it's more of a design issue than a "how do I use this" issue... path::begin() is defined as returning an 'iterator' (not a const_iterator), so I figured I'd be able to write to it. I wrote some code which did something like: fs::path p; /*...*/ for (fs::path::iterator it = p.begin(); it != p.end(); it++) if (*it == "FOO") *it = "BAR"; This errors because operator* on the iterator type returns a const string&. So: was this a deliberate design decision? I don't see anything about this in the design rationale stuff in the docs for Boost.Filesystem. Is there a good reason not to allow people to use the iterator to modify individual path elements? -- Jordan DeLong fracture(a)allusion.net

3 3

Tagged typedef
by Maksym Motornyy 02 Jun '05

02 Jun '05

Hi all, It is know that typedef in C++ is actually an alias, i.e. it doesn't create new distinguishable type. Sometimes this causes problems. Consider following example: typedef int handle; template < typename Value > void write( const Value &value ); void write< int >( const int &value ) { // do processing for int } void write< handle >( const handle &value ) { // we wanted to have separate processing for handle, // but we get only compilation error :( } In my projects I resolve such situations as the following: class handle_tag { }; typedef tagged< int, handle_tag > handle; Then everything works as expected. "tagged" class is actually a wrapper that mimics fundamental type behaviour. Also I have specialization for pointers. Is anyone interested in such solution of given problem? Is it worth to be part of Boost? Sincerely, Maksym Motornyy.

3 4

[filesystem] Windows DLL causes invalid bad path exception
by David Daeschler 01 Jun '05

01 Jun '05

was: [filesystem] WIN32 Can not use drive name in directory I found posts on boost-users from January that describe the problem that I am having. Was there ever a resolution to this? Mr. Dawes, you mention a re-work in the next version of the library ( http://lists.boost.org/boost-users/2005/01/9607.php ) that would fix this problem. Is that rework complete, or not yet? Should I just use the static version for now and not worry about this problem? Comment reference for January 2005 http://lists.boost.org/boost-users/2005/01/9560.php http://lists.boost.org/boost-users/2005/01/9581.php http://lists.boost.org/boost-users/2005/01/9583.php http://lists.boost.org/boost-users/2005/01/9584.php http://lists.boost.org/boost-users/2005/01/9586.php http://lists.boost.org/boost-users/2005/01/9607.php http://lists.boost.org/boost-users/2005/01/9610.php http://lists.boost.org/boost-users/2005/01/9639.php Thank you, - Dave

2 2

Typeof documentation
by Arkadiy Vertleyb 01 Jun '05

01 Jun '05

Hi all, The typeof documentation has been significantly changed. We tried to reflect all the suggestions that came so far during the review. If we missed something please let us know. Please download at: http://boost-sandbox.sourceforge.net/vault/, typeof.zip Also thanks to everybody who helped me to cope with the quickbook/Boost.Book-related issues. Regards, Arkadiy

4 14

Typeof: Review result
by Andy Little 01 Jun '05

01 Jun '05

Hi All, I am pleased to formally announce that the Typeof library has been accepted into Boost. There were 3 reviews, all in favour of accepting the library. This has been a slightly odd review in that the implementation and documentation changed during the review period. However as modifications to the implementation were mainly to improve compile time performance, which is the major weakness of the library, I feel that this should not affect the result. Overall there was a feeling that the documentation could be improved. Following are some of my comments, though views of others would be welcomed.As I understand it the documentation is being reworked, so some of these points may be out of date. 1) The STL support section would be better later. Should there be a formal list of the stl registration libraries, with their headers. The STL headers would also be useful as useage examples with links? 2) A note regarding closing namespaces when registering a type (cited by David Abrahams). and an example in a namespace just to clarify this. 3) Separate examples of each useage with types, templates and values etc (also cited by David Abrahams). . This section of the documentation is slightly short IMO. 4) More information regarding incrementing-registration-group. How will separate inclusions ( eg different order) affect it. eg the index of each type registered cannot be relied on. In fact a statement regarding anything in the implementation being subject to change might also be 5) More information regarding the differences from decltype. e.g. is there a way for the user to simulate decltype more closely, eg by use of remove_reference. Finally.. Thanks to Arkadiy Vertleyb and Peder Holt for all their work. regards Andy Little

7 8

Re: Customer Friendlier Boost Installation
by David Abrahams 01 Jun '05

01 Jun '05

"Johan Nilsson" <r.johan.nilsson(a)gmail.com> writes: > "David Abrahams" <dave(a)boost-consulting.com> wrote in message > news:uhdgi971q.fsf@boost-consulting.com... >> David Abrahams <dave(a)boost-consulting.com> writes: >> > > [snip] > >>> No! It's supposed to check %HOMEDRIVE%%HOMEPATH% first, then %HOME%, >>> then %BOOST_BUILD_PATH%. I'll look at this. >> >> Should be fixed now. >> >>> Just out of curiosity: why weren't HOMEDRIVE and HOMEPATH set in your >>> environment? Aren't they set up for you by Windows? >> >> Still curious, though. > > Me too. I've tried googling as well as searching the MS Knowledge Base but > couldn't find any reference to a similar problem. I'll try the MS > newsgroups. > > FWIW, I can reproduce the problem on both of my XP SP2 machines. ?? I thought Eric was the only one with the problem. Is it fixed now? -- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

[shmem] New Shmem snapshot available in boost vault
by Ion Gaztañaga 01 Jun '05

01 Jun '05

Hi to all! After some busy weeks, I've been working again on Shmem library. This is what you get in the new snapshot I've just placed in Boost Vault: Documentation: -> Ported all documentation to QuickBook. Very little has changed and the real Documentation work starts now. But Quickbook allows direct source file inclusion for examples, syntax highlighting and some other nice features. Suggestions are welcome. -> Apart from the documentation zip in boost.vault, I've put the documentation online in this address (there are banners, but nothing is free...): http://ice.prohosting.com/newfunk/boost/libs/shmem/index.html Bugfixes: -> shmem set-map family iterator bugfix in operator->() -> shmem vector fix in size() -> Added some missing typedefs in STL-like containers New features: -> shmem assoc_vector has died, long live to flat_set/flat_multiset/flat_map/flat_multimap! Based in an ordered vector, the flat associative ordered container family is born as an extension of Loki's AssocVector. shmem_assoc_vector.hpp is provided for backwards compatibility. If you don't like flat_* name, suggestions are welcome for this new classes. Any comment, suggestion or help is welcome. Regards, /Ion

3 5

Google Summer of Code Stipends for student programmers
by Eric Ford 01 Jun '05

01 Jun '05

Might Boost be interested in becoming a "mentoring organization"? That would allow a student to get a summer stipend from Google to write code to contribute to boost. I'd guess that we probably have a few student programmers on the list who have already demonstrated their capabilities and enthusiasm. If so, see below. The deadline is June 14. http://code.google.com/summerofcode.html Cheers, Eric Ford

3 2

std::wstring support in GCC/Cygwin?
by Beman Dawes 01 Jun '05

01 Jun '05

What is the story on std::wstring support with GCC/Cygwin? How do you turn it on? I'm trying to test the Boost.Filesystem i18n branch with more compilers. It is working fine with last model Intel, Metrowerks, and Microsoft on Windows, and GCC on the Mac, but no luck with GCC/Cygwin. --Beman

6 10

Regression testing (1.33)
by Victor A. Wagner Jr. 01 Jun '05

01 Jun '05

Since we seem to be getting close (date anyone?) to the release of 1.33, I've changed my testing cycle to 8 times a day to improve turnaround for the library authors. The only remaining failures in VC-8_0 are some datetime things (the localtime test is clearly a deliberate choice on someone's part to make dates before 1970 "illegal"). Are there any representatives from either Microsoft or Dinkumware here who can explain this decision? Should we mark them as "expected failures" (though I'd object to having the block turn green simply because _I_ beileve it is an error and should show up as such) the two "input facet" test failures show only: Run output [2005-05-31 17:13:49 UTC]: EXIT STATUS: 666 not a lot of information for chasing down the actual problem. Ditto the "errors handling test" in threads, not much to go on. btw, I notice in the threads test that I seem to be the only person running some of the tests? Is there something wrong with the test running scripts? Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

3 2

[iostreams] Progress on regressions
by Doug Gregor 31 May '05

31 May '05

The iostreams regression tests are looking a LOT better. Great! I see that everything is failing on gcc-2.95.3-linux. I'm going to mark this toolset as unusable: nobody expects iostreams-anything to work with GCC 2.95.x's non-templated iostreams, and the maintenance burden far outweighs any advantage. The bzip2, gzip, and zlib tests are failing on Windows. I can't tell if this is a configuration error on the testers' machines or if it's a build issue in the iostreams library. I'll take a shot at reproducing the problem this evening. Doug

4 7

failure building iostreams cvs
by Neal Becker 31 May '05

31 May '05

This is on Fedora 3, with boost cvs. FileClone stage/lib/libboost_filesystem.so.1.33.0 MkDir1 bin/boost/libs/iostreams MkDir1 bin/boost/libs/iostreams/build MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.a MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.a/gcc MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.a/gcc/release ...skipped <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>exception.o for lack of <@boost!libs!iostreams!build>exception.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>operations_posix_windows.o for lack of <@boost!libs!iostreams!build>operations_posix_windows.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>path_posix_windows.o for lack of <@boost!libs!iostreams!build>path_posix_windows.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>convenience.o for lack of <@boost!libs!iostreams!build>convenience.cpp... gcc-C++-action bin/boost/libs/iostreams/build/libboost_iostreams.a/gcc/release/bzip2.o gcc-C++-action bin/boost/libs/iostreams/build/libboost_iostreams.a/gcc/release/zlib.o ...skipped <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>libboost_iostreams.a for lack of <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>libboost_iostreams.a(exception.o)... ...skipped <@boost!lib>libboost_iostreams.a for lack of <@boost!libs!iostreams!build/libboost_iostreams.a/gcc/release>libboost_iostreams.a... [...more failures]

2 1

Why no shared wave?
by Neal Becker 31 May '05

31 May '05

Built cvs today, I noticed that wave only built a static lib, no shared lib. Is this intentional?

2 1

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 31 May '05

31 May '05

> On Behalf Of David Abrahams > Subject: [boost] Re: Customer Friendlier Boost Installation > > "Brian Braatz" <brianb(a)rmtg.com> writes: > > > Wild thought- > > > > Is there a rational way to have a "environment" checker. I am NOT a > > bjam expert- but it would be handy if we had some cmd line program > > that would follow spit out all the info BJAM looks for and finds. > > > > I am slightly half cocked in this idea, but basically it would have to > > be enough information that you could get a better sense for what Bjam > > was doing > > > > Something like > > > > C:\boost\> boostenvcheck.exe ** Enviroment Report** Python is not in > > the path User-config.jam file is setup to use gcc, vc7.1 Etc.... > [David Abrahams Writes:] > If you're talking about user-config.jam you're talking about BBv2. > > First question: how would this information help people? They can go look > at their user-config.jam themselves, right? Hmm.. My apologies for not fully explaining myself. I will explain the concept I am speaking from FROM A GENERAL sense first, and then relate it to boost. BACKGROUND: I have had good success with the following paradigm: GENERALLY, if you have app you are deploying to MANY sites and you need to support those sites, it is extremely valuable to build a program which analyzes the environment and spits out a report. This is useful for both on site techs and trouble shooting over the phone. How you build such a program is ask yourself the following questions: 1- What are the configuration assumptions my application requires? 2- What concepts does my application *assume*? Once you have identified these, you then build an application which allows for introspection of the environment. Generally it is usually something that spits out a report that checks all the "assumptions" of the tools and displays the conformance to the assumptions. Think of this concept as "unit testing" for an environment or product. You can also think of this as a "blood test" for a patient. :) PRACTICE: Generally, over many companies I have worked with, I have had a *DIFFICULT* time getting developers under my leadership to see the value of this thinking. The mental shift for folks with this thinking is "well we should just make sure the systems are configured properly. What you are saying we need to do isn't necessary. The users (or techs) need to learn to read the docs.". In practice I have found applying a tool like this invaluable. Everytime I have gone through this cycle with folks, they EVENTUALLY SEE that value. The pain of trying to support something deployed allows for people to "feel" the value. But it is always hard to get the developers to "go there". This is something I have yet to understand why people have an aversion to this thinking. It can save a company's proverbial butt by significantly reducing the down time and trouble shooting time of an environment. Even if you have standards, and train people, and put systems in place to enforce those standards, chaos always finds a way of creeping in. BOOST: To me this is a piece that is missing that stops wider adoption. I have taken the proposed boost profiler, added A LOT to it, integrated it into a production application and shared the techniques and concepts with my developers. I have purchased the MPL and Modern CPP books for my people and have been busy helping folks implement some modern techniques into their designs. I now have an entire team excited about boost. Extremely excited. Their excitement and the time I have spent fostering that has SLOWED my ability to get a "next cut" of the profiler out for review. REMEMBER: I am not ashamed to recognize myself as the "Village Idiot" on this list. I DO know more about boost and template programming than anyone in my company, but I am in NO WAY SHAPE or form as knowledgeable as the fine people who frequent the list. What is interesting though as I watch this process, is I am SHOWN CLEARLY why boost is not adopted by the normal programmer. Many things the rest of you guys KNOW and take for granted are not easily grasped by people. I believe this pattern forms as people get smart, the things they see as obvious grow in complexity as they become smarter. I noticed the other day a post where someone was NOT getting a concept, the response to the person was basically "Documentation should not cover things that are obvious". That struck me and I have discussed that mail with some of the folks under my leadership, using that as an example to discuss difficulties in communication. I understand boost better than anyone in my company, but I have to tell you it REALLY shows how hard this stuff is to get your head around by watching CLOSELY someone stepping into it for the first time. I have written several samples and have spent hours explaining boost.function for example. This is a lib, most people might see as "obvious" (me included). There are obvious limits to what can be documented, and there is always going to be a barrier to entry. With boost that barrier is huge, I believe it to be bigger than EVEN I initially thought as I try to bring my team up to speed on what I know. HOW THIS THINKING RELATES TO AN ENV CHECKER IN BOOST: On a windows box, one used to be able to run MSD.exe, which would spit out a report for your configuration. XP allows one to still run sysedit.exe. This program is outdated (it is from Win3.1) but it shows you your configuration. In the old days people us3ed these tools to better support the system. I AM NOT a BOOST.BUILD expert. I believe the "how to think about this" I am presenting is valid (I see it everyday working with people using boost for the first time). I am unsure if the explicit idea is valid due to my remaining limited understanding of boost.build. HAVING said that here is the suggestion, reformed: Boostenvcheck.exe become s a program which LISTS the dependencies for your configuration. How to identify WHAT it lists requires someone more knowledgeable than me about it's dependencies and configuration assumptions. Once one has this tool then, just like a general software app, one can say to a newbie on the list "run boostenvcheck.exe" in your boost dir and send the report to the list. If the report is well formed, the people on this list should be able to scan the report and QUICKLY help someone out. Think of this like a "blood test", it measures and reports all the assumptions and parameters. Overtime, just like a doctor, the folks on this list will develop an intuition for the values in the report and be able to quickly help people resolve issues. ( SIDE NOTE: I interviewed a Dr recently (requirements work) and he was telling me about his intuitive sense he has gained over reading blood tests and troubleshooting problems) EXECUTION: (or "Finishing current tasks") :) I am currently working very hard on bringing what I learned about profiling and introspection to this list. I have to take the code I integrated with the app (conforming to internal ways of doing things) and boostify it enough for presentation, it is also gaining scope and functionality and being redesigned. I have been working for the last 6 months on the profiler and moving that forward (not just technical, we have taken my code through QA and put it into production). I regret this has kept me largely off list, but it has been a huge learning experience about "actual" introspection (not just logging or profiling- there is a deeper concept here I am not seeing anyone else address on this list or in this industry) My plan is to do this: - Get the profiler re-written to work alongside the other pieces I have learned are needed - Get this sent out to the list so people can finally SEE what I have been working on (there is a connection to the excellent work John T has been working on with logging- but these two concepts are not mutually exclusive- logging is just one piece of introspection) - Get some of the other pending library submissions I have not had a chance to finish "out there" for people to see and tear apart. - Get "down and dirty" with boost.build and SPEND the time to learn that sucker. Once I have done this, I can then formally propose an actual "working" boostenvchecker program and everyone have an easier time "seeing" what I am talking about. In general, I LOVE BOOST, and have devoted as much time as I can suck out of my production world to finding ways to contribute my perspective. I have taken to going to bed REALLY early so I can get up early every morning and work on bringing the profiler \ tracer to boost. I am now getting in a good 6-8 hour day prior to my work day starting. There are so many things I would like to contribute. I believe my "village idiot" perspective, if executed correctly, can provide considerable aid to people adopting boost. I just simply have to focus enough effort to SHOW people what I am talking about. Sample code \ tools communicate better than words sometimes. If someone "sees" what I am talking about and wants to move if forward before I get there. ALL THE BETTER. :) Sorry for the long response. But what I have explained for anyone reading this is where I am coming from. Anyone who follows this will see a consistency between this mail, past mails, and future actions. > > First problem: .jam files are programs, not just configuration, like > .ini files. We can't capture everything a user might want to write > there in English. > > > I have been using boost for (has it been that long) 2 years now. Bjam > > still confounds me. ( I appreciate the work effort, it is a cool tool, > > I remain struggling with it though) > [David Abrahams Writes:] > You never post questions; how can we improve its interface and help > you understand it otherwise? > Excellent point indeed. I need to do more of this. I tend to take a LONG TIME to learn something, once I have it, I have it well. But the first initial barrier is tough, and my initial questions are frequently so idiotic I don't always get the information by asking the question. I have read the MPL book now FIVE TIMES cover to cover. On the fith pass, I "saw it". (the mpl::for_each<> is what kicked it in for me) I have been now writing programs using the MPL library (kudos to both you and Aleksey- excellent body of work). Because I know I have to go through this learning process, I work very hard up front to "see it" enough so I can answer my own conceptual questions first. Basically though, your advice is well received by me. I need to ask more questions, and will do so in the future. I have a personal goal of learning everything I can about boost as this will help me contribute. > > (I am also a tad frustrated because I have been trying to make vc7.1 > > build wave for the last 5 hours) > > > > Semi-Related: > > > > I proposed (a long time ago) building a SIMPLE gui framework- with > > the core elements, and then making a "boost environment checker" out > > of that- I.e. imagine a tree control with all the types of settings > > and what nots, and the ability to navigate this gui to try to > > determine what is not set correctly. > > Might be a good idea; we can't really know until we see one, though. [Brian Braatz Writes:] YES. THIS IS THE BANE OF MY EXISTANCE. So much to code, so little time. :) I realize I "come from a different place" in my thinking. And I realize that to truly communicate what I am talking about I have to show it. I am just frustrated than I require sleep. If I didn't need sleep I could spend more time learning more about boost. :) CONCLUSION: Dave- Thank you very much for your thoughts and advice. Everyone- I see everyday in people I am working with the incredible hair raising effect and energizing influence bringing boost into my dev team has had. I am grateful for everyone's dedication to creating some incredible works. THANK YOU ALL, "The Village Idiot" :)

2 1

RE: [boost] Re: Customer Friendlier Boost Installation
by Martin Bonner 31 May '05

31 May '05

----Original Message---- From: Rob Stewart [mailto:stewart@sig.com] Sent: 31 May 2005 14:28 To: boost(a)lists.boost.org Cc: boost(a)lists.boost.org Subject: Re: [boost] Re: Customer Friendlier Boost Installation > From: =?UTF-8?B?TWljaGVsIEFuZHLDqQ==?= <michel.andre(a)swipnet.se> >> Rene Rivera wrote: >>> I'm not sure "libs", or "Libraries", or "Library Files", fits in >>> this case because we are talking about both programs(bjam, wave, >>> etc.) and libraries. And the other examples, Python, MinGW, etc. >>> also install programs. A more appropriate location would be: >>> >>> "\Development Files\Boost" >>> "\Development Files\Python" >>> "\Development Files\MinGW" >>> ... >>> >>> Although the shorter "\Development\*" would probably works as well. >>> But if we are talking about such a location you need to consider >>> language localization, in the same way as "Program Files" treated. >> >> Personally I have >> \Packages\boost > > I always use <drive>:\dev or $HOME/dev, depending upon platform. > "dev" is short and sweet. I think what this proves is that the location needs to be user selectable! -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

octonion_test and quaternion_test failures on Intel 8.1/Windows
by Beman Dawes 31 May '05

31 May '05

Both octonion_test.cpp and quaternion_test.cpp, at about line 94, contain the following: // Provide standard floating point abs() overloads for MSVC //#if BOOST_WORKAROUND(BOOST_MSVC, < 1300) || (defined(_MSC_EXTENSIONS) && BOOST_MSVC < 1310) That looks like a workaround for the fact that prior to VC++ 7.1, the Microsoft C library did not define abs(float) etc. if _MSC_EXTENSIONS was defined. The Intel compiler uses the Microsoft libraries, and defines _MSC_EXTENSIONS, but of course BOOST_MSVC is not defined. That causes the workaround code to be included, resulting in multiple definitions, if the Microsoft library 1310 (7.1) or later is being used. I believe the corrected code should read: // Provide standard floating point abs() overloads if older Microsoft // library is used with _MSC_EXTENSIONS defined. This code also works // for the Intel compiler using the Microsoft library. #if defined(_MSC_EXTENSIONS) && defined(_MSC_VER) && _MSC_VER < 1310 I've committed this change to CVS for both source files on the assumption that this suits the library maintainer. If not, or there is something wrong with the fix, please feel free to revert the changes. --Beman

3 2

Problem with serialization mersenne_twister with cvs
by Neal Becker 31 May '05

31 May '05

This used to work with 1.32.0, but is failing with cvs. In mersenne_twister.hpp, I add template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & x; ar & i; } Now compile: g++4 -g -DNDEBUG -O3 -ftree-vectorize -msse2 -ffast-math -fstrict-aliasing -Wall -fPIC -I/usr/local/src/boost.cvs -I/usr/include/python2.4 -I/home/\ nbecker/shannon2.darcs/src -c -o boost_rand.os boost_rand.cc /usr/local/src/boost.cvs/boost/archive/detail/oserializer.hpp: In function 'void boost::archive::save(Archive&, T&) [with Archive = boost::archive:\ :binary_oarchive, T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346425566u\ >]': /usr/local/src/boost.cvs/boost/archive/basic_binary_oarchive.hpp:69: instantiated from 'void boost::archive::basic_binary_oarchive<Archive>::save\ _override(T&, int) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346\ 425566u>, Archive = boost::archive::binary_oarchive]' /usr/local/src/boost.cvs/boost/archive/binary_oarchive.hpp:47: instantiated from 'void boost::archive::binary_oarchive_impl<Archive>::save_overri\ de(T&, int) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18, 3346425566u\ >, Archive = boost::archive::binary_oarchive]' /usr/local/src/boost.cvs/boost/archive/detail/interface_oarchive.hpp:89: instantiated from 'Archive& boost::archive::detail::interface_oarchive<A\ rchive>::operator<<(T&) [with T = boost::random::mersenne_twister<uint32_t, 32, 624, 397, 31, 2567483615u, 11, 7, 2636928640u, 15, 4022730752u, 18,\ 3346425566u>, Archive = boost::archive::binary_oarchive]' boost_rand.cc:41: instantiated from here /usr/local/src/boost.cvs/boost/archive/detail/oserializer.hpp:557: error: invalid application of 'sizeof' to incomplete type 'boost::STATIC_ASSERTI\ ON_FAILURE<false>'

4 6

[iostream] Odd errors on build from BOOST_ROOT
by Jeff Garland 30 May '05

30 May '05

I got some weird errors out of iostreams that look like it's complaining about the serialization lib files? This only happened when I compiled from BOOST_ROOT -- everything was fine when I compile from iostreams/build. I'm assuming this is some sort of Jamfile issue... This was a fresh CVS checkout as of this morning -- built on Linux. Jeff ----- MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc/release MkDir1 bin/boost/libs/iostreams/build/libboost_iostreams.so/gcc/release/shared-linkable-true ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_archive.o for lack of <@boost!libs!iostreams!build>basic_archive. cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_iarchive.o for lack of <@boost!libs!iostreams!build>basic_iarchiv e.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_oarchive.o for lack of <@boost!libs!iostreams!build>basic_oarchiv e.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_iserializer.o for lack of <@boost!libs!iostreams!build>basic_iser ializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_oserializer.o for lack of <@boost!libs!iostreams!build>basic_oser ializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_pointer_iserializer.o for lack of <@boost!libs!iostreams!build>ba sic_pointer_iserializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_pointer_oserializer.o for lack of <@boost!libs!iostreams!build>ba sic_pointer_oserializer.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_serializer_map.o for lack of <@boost!libs!iostreams!build>basic_s erializer_map.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_text_iprimitive.o for lack of <@boost!libs!iostreams!build>basic_ text_iprimitive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_text_oprimitive.o for lack of <@boost!libs!iostreams!build>basic_ text_oprimitive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>basic_xml_archive.o for lack of <@boost!libs!iostreams!build>basic_xml_ archive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>binary_iarchive.o for lack of <@boost!libs!iostreams!build>binary_iarch ive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>binary_oarchive.o for lack of <@boost!libs!iostreams!build>binary_oarch ive.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>extended_type_info.o for lack of <@boost!libs!iostreams!build>extended_ type_info.cpp... ...skipped <@boost!libs!iostreams!build/libboost_iostreams.so/gcc/release/shared-linkable-true>extended_type_info_no_rtti.o for lack of <@boost!libs!iostreams!build>e xtended_type_info_no_rtti.cpp...

3 5

Patch for BOOST_OLD_IOSTREAMS detection
by Matthias Troyer 30 May '05

30 May '05

Hi, Several places in Boost try to detect BOOST_OLD_IOSTREAMS using the following ifdefs: // support for pre 3.0 libstdc++ - thanks Phil Edwards! #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) # define BOOST_OLD_IOSTREAMS #endif This incorrectly defines BOOST_OLD_IOSTREAMS for the Cray X1 C++ compiler. Could this be changed to include an && !defined(__crayx1) or something similar as in: #if defined (__STL_CONFIG_H) && !defined (__STL_USE_NEW_IOSTREAMS) && !defined(__crayx1) # define BOOST_OLD_IOSTREAMS #endif Three offending files are: boost/dynamic_bitset/config.hpp boost/range/iterator_range.hpp libs/dynamic_bitset/example/timing_tests.cpp Maybe it would be best to move this to the global config file? Best regards Matthias

3 4

[BGL] Comparison with LEDA
by Sylvain Pion 30 May '05

30 May '05

You may find this comparison with some LEDA graph algorithms interesting : http://www.algorithmic-solutions.com/leda-outperforms-boost.htm -- Sylvain

1 0

[gauging interest] Windows GUI - semi-installer
by Pablo Aguilar 30 May '05

30 May '05

Hi, After reading the "Customer Friendlier Boost Installation" thread, I've now enough motivation to get into this... I've been planning a boost GUI semi-installer, but hadn't gotten around to it due to lack of time. I call it "semi" in the sense that it wouldn't be the typical "wizard like" installer everyone's used to, but rather a configuring utility for (at least) the IDEs I'm familiar with. Here's what I thought it should do: 1) Register include/lib directories with VCx 2) Don't know how yet, but try the same with BCB (as I think it's on a per-project basis, rather than global settings like VC) 3) Allow building of libraries which require it, with the following options: - Which compiler(s) to use? - Which configuration (debug/threading/static/etc) for each compiler? I believe that detecting which libraries need building would just be a matter of searching for a "build" subdirectory within a given library's directory. Don't know about configurations, though, maybe some simple parsing of the jamfiles would do.. The reason I chose not to do it as an installer, is because I'm far more comfortable with developing GUIs with say, BCB, than I am with the installer programs I've tried. Comments, suggestions, requests are welcome. Pablo Aguilar

5 18

[range] Borland and GCC-2.95 workarounds for iostreams
by Jonathan Turkanis 30 May '05

30 May '05

Hi Thorsten, I made two changes to range, which should only affect gcc-2.95 and Borland: - in begin.hpp and end.hpp I applied some of the Borland workarounds to gcc-2.95 as well - in iterator_range.hpp, I removed some Borland workarounds which were causing iostreams to fail on Borland, and which did not seem to be necessary. The same tests passed with and without the workarounds. Jonathan

2 6

[Typeof] Formal Review in progress
by Andy Little 30 May '05

30 May '05

Hi All, A reminder that the Typeof Formal Review is currently in progress and runs until May 30th. So far there have been only two reviews, both in favour of the library. (Thanks again to both those reviewers for their time and energy). Nevertheless it would be nice to get some more opinion, affirmation , etc regarding this important library. One area in particular that has been cited as worthy of improvement is the documentation, so please download the library and take a look at it. (And then write a review ;-) ) Are there enough examples? Is there enough information regarding how to use the library. Is it workable in a large project?. is the effect on compile time a problem.? etc. I'm sure that Arkadiy and Peder would welcome feedback on the documentation in particular so that they can improve it. So please try to find time to write a review. The proposed Typeof library emulates the functionality of the non-standard 'typeof' operator, and incomplete implementations of decltype and the proposed 'auto' declarator , described in http://www.osl.iu.edu/~jajarvi/publications/papers/decltype_n1478.pdf. It is commonly acknowledged that this type of functionality is sorely needed and should be standardardised in the language. For compliant compilers the library requires some help in the form of registration macros but, because use of typeof is by its nature most likely in generic libraries, it is expected that this can often be done by the library author rather than the user. In some cases the compilers capabilities (by means of extensions and even compiler bugs) have been used to remove the need for registration. However, for portability and in order to test emulation mode on the compilers where it is available but not used by default (VC7.1, GCC etc), #define BOOST_TYPEOF_COMPLIANT [see note *1*]. Testing the emulation is useful, even on compilers that provide a better option, to get a rounded view of the library and its capabilities. I hope you will find time to write a review of the library, which is available at: http://boost-sandbox.sourceforge.net/vault/ , typeof.zip The system has been tested with the following compilers: MSVC 6.5/7.0/7.1/8.0; [see note *1* regarding VC7.0 and VC6.5] GCC 3.4.2 (The following is a quote from : http://www.boost.org/more/formal_review_process.htm ) Here are some questions you might want to answer in your review: What is your evaluation of the design? What is your evaluation of the implementation? What is your evaluation of the documentation? What is your evaluation of the potential usefulness of the library? Did you try to use the library? With what compiler? Did you have any problems? How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? Are you knowledgeable about the problem domain? And finally, every review should answer this question: Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Andy Little Typeof review manager notes: *1* MSVC6.5 and VC7.0 are not supported by the BOOST_TYPEOF_COMPLIANT macro

6 34

Typeof: Formal Review period ended
by Andy Little 30 May '05

30 May '05

Hi, The Typeof formal review period is closed. Thanks to all those that participated in the review. Thanks also to Tom Brinkman, the review Wizard. I hope to provide a more detailed summary of the review shortly, meanwhile I am happy to say that the Typeof library has been accepted into boost. regards Andy Little

1 0

Yet another quickbook question
by Arkadiy Vertleyb 29 May '05

29 May '05

Hi all, How do I generate the document-level index in the quickbook? Right now it generates indexes for those sections that contain subsections, but not the top-level index. Regards, Arkadiy

3 4

[parameter] Comments and concerns
by Cromwell Enage 29 May '05

29 May '05

1. For type extraction, the name "binding" is *much* better than the name "index_result". 2. With regard to the rvalue issue recently tackled by Dave Abrahams and Daniel Wallin: 2.1. In my projects, I seldom assign a possible rvalue to a const reference; I almost always use a const variable. The functions for which I require named parameters are initializer functions; that is, they build containers, graphs, mazes, etc. The cost of making even several copies of mostly primitive objects is negligible in comparison. 2.2. The handful of times I do bind an rvalue to a const reference, I don't even need the object; I just want its type, and the static functions associated with it. All in all, no problems here. 3. By default, most of the property maps used by the BGL are created in the following manner: make_iterator_property_map( std::vector<ValueType>( num_vertices(graph) ).begin() , index_map , ValueType() ); Assuming such a call is expensive enough that it should be a lazy default, the corresponding code (if I'm not mistaken) would be: typedef typename property_map<Graph,vertex_index_t>::type VertexIndexMap; ... typedef std::vector<ValueType> ValueVector; ... VertexIndexMap index_map = get(vertex_index_t(), graph); ... function_impl( graph , p[ some_named_parameter || bind( &make_iterator_property_map< typename ValueVector::iterator , ValueType , VertexIndexMap > , ValueVector(num_vertices(g)).begin() , index_map , ValueType() ); ] , ... ); 3.1. A new user may easily neglect to specify the template parameter types by naively expecting Boost.Bind to accept function templates just as it does ordinary functions. (I sure did.) This is not a Boost.Parameter issue per se, but if one expects to commonly use Boost.Bind to produce lazy defaults, perhaps a gentle warning would be in order. 3.2. BTW, according to <http://www.boost.org/libs/property_map/iterator_property_map.html>, ValueType and IndexMap should be the third and second template parameters, respectively. Should <boost/property_map.hpp> be fixed to match its documentation? 3.3. These are minor issues for me, but they may be major concerns for Doug Gregor, Jeremy Siek, et al. if they're revamping the BGL to use Boost.Parameter. 4. Ah, the joys of GUI programming... 4.1. Even the simplest WxWidgets program grinds to a halt when calling a function that uses the Boost.Parameter mechanism. The same goes for FLTK and FOX. 4.2. OTOH, Irrlicht <http://irrlicht.sourceforge.net/> gives full cooperation. The only apparent difference between this library and the others (aside from the fact that it is mainly a 3D library) is that it opens up a DOS box in the background. IIRC a similar concern was posted a while back, I think wrt Boost.Test + GUIs. 4.3. I haven't had the time to produce simple test cases. If you want them, let me know. Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

Synchronize Pointer (thread safe wrapper)
by Axter 29 May '05

29 May '05

Is there any interest in adding to the boost library a synchronized pointer class which is a thread safe wrapper class for an object instance. If so, please examine the following source code, and please post feedback. http://code.axter.com/sync_ptr.h http://code.axter.com/sync_ctrl.h Or you can download it from the boost sandbox. It's listed as sync_ptr.zip The following link has the source code for a test case application: http://code.axter.com/TestCaseAppforThreadSafeObject_sourcecode.zip

2 2

RE: [boost] Re: Collecting Users/Usage of Boost (was A more confrontingBoost (long))
by Brian Braatz 29 May '05

29 May '05

> -----Original Message----- > On Behalf Of Loïc Joly > David Abrahams a écrit : > > > I don't think we need to do that kind of diligence. If we have heard > > from someone who we have reasonable confidence works for the company, > > that should be enough. If a company asks us to, we can always remove > > mention from the site. I do think it would be wrong to use a logo > > without special permission from someone in authority, but companies > > don't have any special right to control information about their use of > > Boost. > > Well, I'm not sure, but I think that many companies have some very > strict policies about how their names are used, and even more their logos. > > I use boost at work in my company. But I guess that if I told you to use > this company name, without checking with the company lawers and the > communication department, I would get into trouble. > > What might happen is that many small companies would agree easily, but > very few big companies, where administrative stuff is more > "brazil-like". I'm not sure wether seing many name I've never heard of > and no known name would be good or bad advertising. So I suggest that > before getting such a page online, it would be good to wait until there > are enough names, with some well knows ones. > [Brian Braatz Writes:] Yes. Some will have this problem. I sympathize. Allow me to offer up that the because Adobe has released a framework that sits on top of boost that this would help the issues you raise. Only the people who watch this list will KNOW that though. So if we had a products page, and we had a link to the adobe framework in addition to others, it might help speak to the problem of people not seeing boost as a viable path. Btw- I found the python link fascinating. An additional suggestion would be to have SITE MAP on boost.org. I keep seeing boost pages in these mails I never knew existed (the phyton projects page is one)

2 1

quickbook formatting problem
by Arkadiy Vertleyb 29 May '05

29 May '05

Hi all, I am now having a problem formatting the source code in the quickbook. As documentation suggests, I put tab in front of the source code, and it appears preformatted in the browser, however there is no syntax hilighting nor gray backround. What could be wrong? Thanks, Arkadiy

7 16

Regression gone
by Victor A. Wagner Jr. 29 May '05

29 May '05

The regression page is missing "page not found" and has been for a while. Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

lexical_cast with default value
by Dave Dribin 29 May '05

29 May '05

Hi all, I recently discovered lexical_cast, and it's very nice and elegant. I'd like to put in a feature request, though: the ability to use a default value rather than throwing an exception on conversion failure. Basically, it would take a second argument that would be the value returned if the conversion fails. This could be used directly in the example, like: std::vector<short> args; while(*++argv) { args.push_back(lexical_cast<short>(*argv, 0)); } This eliminates the throwing and catching of an exception for cases where conversion failure is not an exceptional. I've attached a patch to lexical_cast.hpp found in Boost 1.32.0 -Dave

6 18

Documentation error?
by Raz 28 May '05

28 May '05

I was looking in the Boost Assignment library and I noticed this code under the "Function operator+=()" heading: [CODE] #include <boost/assign/std/vector.hpp> // for 'operator+=()' #include <boost/assert.hpp>; using namespace std; using namespace boost::assign; // bring 'operator+=()' into scope { vector<int> values; values += 1,2,3,4,5,6,7,8,9; // insert values at the end of the container BOOST_ASSERT( values.size() == 9 ); BOOST_ASSERT( values[0] == 1 ); BOOST_ASSERT( values[9] == 9 ); } [CODE] Shouldn't the last assertion be BOOST_ASSERT(values[8]==9)? Unless my brain is tricking me, the last element in the container should be at the 8th slot. -- ------------------------------------------- Dan Day http://razzerblog.blogspot.com

3 2

Re: [boost] serializatation const change (was Re: Problem withserialization mersenne_twister with cvs)
by JOAQUIN LOPEZ MU?Z 28 May '05

28 May '05

----- Mensaje original ----- De: Jeff Garland <jeff(a)crystalclearsoftware.com> Fecha: Sábado, Mayo 28, 2005 8:06 pm Asunto: Re: [boost] serializatation const change (was Re: Problem withserialization mersenne_twister with cvs) > On Sat, 28 May 2005 10:05:15 -0700, Robert Ramey wrote [...] > > I don't see this change as "breaking code" but rather detecting > code > > that is very likely already broken. > > > > So, as I said, its not that I'm unsympathetic to your point of > view, > > I just don't think everyone is sympathetic to mine. > > Well, I'd say that 'no one' is sympathetic to yours, yet ;-) I > don't think > that Vladimir, myself, or the others that have posted on this > topic are > convinced that this change is really going to prevent people from > making the > error you are concerned about. For the record, not that I'm in love with the stricter const rules either, but I must confess that, when hit by them the first time, they actually uncovered a (potential) problem in my test code. So... I've been thinking about this issue, and my impression is that regular code won't be hit as much as one might think. Typically, serialization is used like this in a program: class my_class { // add serialziation capabilities }; void save(const my class&) { // some file-opening work prior to actual saving ... } void load(my_class&) { // some file-opening work prior to actual loading ... } A typical program will have a centralized point of usage of serialization, and the usual const-abiding rules won't collide with Boost.Serialization. Now, a test program like the ones we've been writing to check the serialization capabilities of our libs is more likely to follow this pattern: std::ofstream ofs(..); archive::text_oarchive oa(ofs); my_class_1 c1; ... my_class_n cn; ... oa<<c1; ... oa<<cn; std::ifstream ifs(..); archive::text_iarchive ia(ofs); my_class_1 cc1; ... my_class_n ccn; ... ia>>cc1; ... ia>>ccn; BOOST_CHECK(c1==cc1); ... BOOST_CHECK(cn==ccn); and here we *do* run into the const problem. The key difference is that, in the latter pattern of usage, we are creating local classes just to check whether they're properly archived and restored. In a real program, the serialization code is typically provided a class to archive from the outside, as serializating classes created on the fly doesn't make much sense after all. Get my point? So, to sum it up, although I think stricter const rules won't prevent as many problems as desired, I think most users won't notice anyway. We lib testers belong to a different flock. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

3 3

autolinking and serialization status
by Robert Ramey 28 May '05

28 May '05

Just in case anyone's interested: I've been struggling to reconcile the problem whereby including a header from boost/serialization/* provokes the autolinking code to request that one of the serialization libraries be included in the link. The problem is that this library is requested even though there are no pending undefined symbols. So what works fine without autolinking - no missng symbols so the serialization*.lib is not needed fails with autolinking where the library is requested even though it contains no undefined symbols. This shouldn't add any code but it is a pain in the neck to require a library when it is really not needed. I'm still working on this - but it turns out harder than it looks for reasons that are too tedious to go into here. Robert Ramey

2 1

RE: [boost] Re: IDE projects/extensions to support Boost.Build
by Brian Braatz 28 May '05

28 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Shishir Ramam > Sent: Friday, May 27, 2005 11:50 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] Re: IDE projects/extensions to support Boost.Build > > On 5/27/05, Andrey Melnikov <melnikov(a)simplexsoft.com> wrote: > > Reece Dunn wrote: > > > David Abrahams wrote: > > > > > What is really needed is a project-generation toolset so you could do > > > something like: > > > > > > bjam release debug msvc-project-7.1 > > > bjam release eclipse-3.0 # release only project files > > > > > > And you end up with the requested project/solution files. I will have > a > > > go at writing such a toolset. > > > > Is it really needed? Earlier in the street Reece proposed two > > *alternative* solutions: > > > > * conversion tool to convert to your favorite IDE format; > > * hook-ins to allow BBv2 projects to be managed in your favorite IDE. > > > > > > P.S. Can anyone look at BCB/CW extension capabilities and find the > > easiest way to get them supporting Boost.Build projects? > > Why not generate CMake (http://cmake.org) input from bjam? > It seems to work well from my limited experience on VC projects and > Makefiles. > > Support exists for Borland and various Visual Studio flavors. > XCode and CodeWarrior seem to in the works. > > Other pros: It's open source, and support from developers on the list has > been > excellent in my experience. > > -shishir [Brian Braatz Writes:] Interesting thought, though what is fuzzy for me is the value of using CMAKE over Bjam. (Cmake appears to take a mini-dsl lang to generate specific make files- whereas bjam, concepeptually seems to do this internally) (<< please don't flame me if I have this wrong :) ) What I do: I have a SED script with vcproj file templates and generate solution files for VC70,VC71, and VC80. If all of your targets are of the same type (i.e. console application), this works reasonably well. Example: C:\temp>MakeBoostTest Me Creating .\Me Creating .\Me\_Prj Creating .\Me\_Prj\MsVc_V71 Creating .\Me\_Prj\MsVc_V70 Creating .\Me\_Prj\MsVc_V80 Creating .\Me\_Prj\DevCpp_V4991 Generate cpp file at .\Me\Test_Me.cpp Generate project file at .\Me\_Prj\MsVc_V70\Test_Me.vcproj Generate project file at .\Me\_Prj\MsVc_V71\Test_Me.vcproj Generate project file at .\Me\_Prj\MsVc_V80\Test_Me.vcproj Generate project file at .\Me\_Prj\DevCpp_V4991\Test_Me.dev Generating cvsadd bat file cvsadd_Me.bat The "TestMe.cpp" is a console app which is all setup for building against boost test. (attached to this mail) All the user has to do after typing "MakeBoostTest" is open the appropriate proj file in the IDE and start typing. I would be happy to share the vcproj files I use, and the SED scripts which generate these. This could be used to generate vcproj files (and any other ide from any other vendor). In MY shop we are not yet jusing Boost.build. Eventually we will get there. Most of my developers work straight out of the MSVC ide. I eventually want to bring in Boost.build and use it for our projects and I eventually want to make this generation script also spit out bjam. In the FAR off future, I would like to build a tool which lets me generate a .vcproj file FROM a JAMFILE and vice versa. The JAMFILE is nice for running tests against multiple compilers, the vcproj file is nice inside because that is what our people work out of. If anyone is interested I will share these scripts.

1 0

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 28 May '05

28 May '05

> -----Original Message----- > On Behalf Of Reece Dunn > Brian Braatz wrote: > > > Paul A Bristow a écrit : > > > * Finally, installing boost takes longer than installing VC++... Is > > > building from the source such an important point ? Would'nt it be > > > possible to provide pre-built libraries for the 3 or 4 main compilers > on > > > windows with each release ? The whole package, zipped, is 80mb on my > >VC8. > >[Brian Braatz Writes:] > >Thank you for also suggesting that. > > Why not make it configurable as part of the install: > > [0] Dependancies: check for Python, cygwin, xsltproc, doxygen, etc. > allowing the user to configure these ("I have Python installed here..."). > [1] Get Boost from... [local directory, boost-consulting, sourceforge, > CVS > (requires a CVS client), ...] > [2] Select the compilers/versions I want to use Boost on (auto-detected > and > configurable list -- add compilers/versions not on the list, select "(do > not) support" > [3] Select which parts of Boost the user whats to install/build > [4] Tools: get prebuilt version of bjam/wave/quickbook or build from > distribution (with compiler...) > [5] List prebuild libraries so I can select the compilers/versions I want > to support > [6] Build libraries for the compilers/versions I want to support (that I > haven't downloaded prebuild versions for) > [Brian Braatz Writes:] Yes that sounds good. The key is to REDUCE the barrier to entry. Especially #5, I know that is work to make it happen, But I believe this to be a major step in spreading boost.

1 0

[type_traits] is_pointer<noncopyable> fails on CodeWarrior 9.4
by Jonathan Turkanis 28 May '05

28 May '05

Hi, The following program produces a compiler error on CodeWarrior 9.4 (see error messages at end): #include <boost/noncopyable.hpp> #include <boost/type_traits.hpp> int main() { bool b = boost::is_pointer<boost::noncopyable>::value; } If I change this to: #include <boost/noncopyable.hpp> #include <msl_utility> int main() { bool b = Metrowerks::is_pointer<boost::noncopyable>::value; } everything is fine. What's up? Jonathan --------------------------- Error : illegal access from 'boost::noncopyable_::noncopyable' to protected/private member 'boost::noncopyable_::noncopyable::noncopyable(const boost::noncopyable_::noncopyable &)' (point of instantiation: 'main()') (instantiating: 'boost::is_pointer<boost::noncopyable_::noncopyable>') (instantiating: 'boost::detail::is_pointer_impl<boost::noncopyable_::noncopyable>') (instantiating: 'boost::is_member_pointer<boost::noncopyable_::noncopyable>') (instantiating: 'boost::is_member_function_pointer<boost::noncopyable_::noncopyable>') (instantiating: 'boost::detail::is_member_function_pointer_impl<boost::noncopyable_::noncopyable >') (instantiating: 'boost::detail::is_mem_fun_pointer_select<false>::result_<boost::noncopyable_::n oncopyable>') is_member_function_pointer.hpp line 70 ));

6 12

boost::array fails ContainerConcept check in 1.32 [patch]
by Michael B. Edwin Rickert 28 May '05

28 May '05

I hope I've got the right list here (first time poster), my apologies if I don't :-). boost::array fails a ContainerConcept check in 1.32 due to it's lack of a const_pointer typedef: #include <boost/array.hpp> #include <boost/concept_check.hpp> int main ( void ) { using namespace boost; function_requires< ContainerConcept< array< int , 5 > > >(); } Resulting errors using MinGW's GCC 3.4.2: boost/concept_check.hpp: In instantiation of `boost::ContainerConcept<boost::array<int, 5u> >': boost/concept_check.hpp:48: instantiated from `void boost::function_requires(boost::mpl::identity<T>*) [with Concept = boost::ContainerConcept<boost::array<int, 5u> >]' ../main.cc:7: instantiated from here boost/concept_check.hpp:683: error: no type named `const_pointer' in `class boost::array<int, 5u>' I noticed the BCCL links to SGI's documentation for the Contanier concept, which actually does not appear to list a const_pointer (see http://www.sgi.com/tech/stl/Container.html) although it does include pointer, which array is lacking. As allready mentioned, I tried this with 1.32 - I also tried the CVS head version, no idea if that's the latest that I should be checking or what (CVS newbie), but this wasn't fixed in there. In any case, adding const_pointer to array allows the simple example to compile - here's a patch which adds this and pointer (hopefully in an OK format - I'm a solo hobbyist, not used to working on large projects) which adds them... let me know if I can be of any other help :-). Index: array.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/array.hpp,v retrieving revision 1.23 diff -u -r1.23 array.hpp --- array.hpp 9 Sep 2004 13:59:00 -0000 1.23 +++ array.hpp 28 May 2005 00:58:03 -0000 @@ -50,6 +50,8 @@ typedef const T* const_iterator; typedef T& reference; typedef const T& const_reference; + typedef T* pointer; + typedef const T* const_pointer; typedef std::size_t size_type; typedef std::ptrdiff_t difference_type;

2 2

RE: [boost] Re: [gauging interest] Windows GUI - semi-installer
by Brian Braatz 28 May '05

28 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > Sent: Thursday, May 26, 2005 12:45 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: [gauging interest] Windows GUI - semi-installer > > "Pablo Aguilar" <pablo.aguilar(a)gmail.com> writes: > > > Yesterday, when I decided to start this, I went and downloaded John > Torjo's > > Win32GUI library (www.torjo.com) and noticed that the build utility > > packaged with it, is very similar to what I originally had in mind. > > > > Like I said, I didn't conceive it as an installer, but rather as a tool > to > > build and setup directories, all this while assuming the user would be > > willing to download and extract boost on his own. > > Sounds helpful. [Brian Braatz Writes:] I restate my suggestion ifrom the past for John to take his Win32GUI library , boostify it, and turn it into a "min-gui" library. THE POINT is to scope it SMALL, I.e. this is a minimal gui library, not QT or WxWindows. Just a small thing that is cross platform but provides simple GUI functionality for boost tools. (similar in scope and concept the tinyxml lib buried in boost)

2 1

[serialization/vc7.1]: integral_c_tag not member of boost::mpl: need help!!
by Francis ANDRE 28 May '05

28 May '05

Hi Robert I ask again for any help on this point since I am now stack with this error. Join my previous mail and your answer about this integral_c_tag ---------------------------------------------------------------------- Hi Robert I got this error from error C2039: 'integral_c_tag' : n'est pas membre de 'boost::mpl' Here the beginning of level.hpp I got: ---------------------------------------------------------------------------- ------ #include <boost/mpl/int.hpp> #include <boost/mpl/integral_c.hpp> #include <boost/serialization/level_enum.hpp> #include <boost/serialization/traits.hpp> namespace boost { namespace serialization { // default serialization implementation level template<class T> struct implementation_level { template<class U> struct traits_class_level { typedef BOOST_DEDUCED_TYPENAME U::level type; }; typedef mpl::integral_c_tag tag; // <== problem here // #if BOOST_WORKAROUND(__IBMCPP__, BOOST_TESTED_AT(600)) // typedef ---------------------------------------------------------------------------- -------- >From what I check of the latest HEAD release from CVS, it should be integral_c instead of integral_c_tag?? Regards FA _______________________________________________ Francis ANDRE wrote: > Hi Robert > > I got this error from error C2039: 'integral_c_tag' : n'est pas > membre de 'boost::mpl' > > >> From what I check of the latest HEAD release from CVS, it should be > integral_c instead of integral_c_tag?? > Hmmm - I looked into this and I don't think its an error. level and tracking are mpl "integer types" with special "sauce" and I think that this is what ineger_c_tag is meant to be used for. Also I note that none of our tests flag this as an error. I'm not all together sure about this so anyone is free to help out here. Robert Ramey

2 2

Electrical outage and downtime 6am-8pm June 5th
by David Abrahams 28 May '05

28 May '05

-- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: [boost] Re: compressed_pair requirements?
by JOAQUIN LOPEZ MU?Z 27 May '05

27 May '05

----- Mensaje original ----- De: Peter Dimov <pdimov(a)mmltd.net> Fecha: Viernes, Mayo 27, 2005 11:10 pm Asunto: Re: [boost] Re: compressed_pair requirements? > JOAQUIN LOPEZ MU?Z wrote: > > > IMHO, std::pair default ctor should be defined as > > > > pair():first(),second(){} > > This doesn't change things. pair() {} is what you probably want. Why? (This is not a rethoric question, my understanding of value-initialization matters is so poor.) > > What can I say, I'm glad that your and Howard's view didn't > prevail when > std::pair was being defined. If I had it MY way, > > typedef set<int> int_set; > pair<int_set::iterator,int_set::iterator> p; > > would have compiled on no compiler because int_set::iterator > wouldn't even > have had a default constructor. I think there's some value in having iterators being DefaultConstructible. Otherwise you're forced to have some container around everytime you construct an iterator. Defaut construction for iterators is roughly the equivalent of initializing to 0 in the case of pointers. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[bind] Usage with function templates
by Cromwell Enage 27 May '05

27 May '05

A new user may naively expect Boost.Bind to accept function templates just as it does ordinary functions. For example: std::map<Vertex,Vertex> vertex_map; boost::prim_minimum_spanning_tree( graph , boost::make_associative_property_map( vertex_map ) ); works just as well as std::map<Vertex,Vertex> vertex_map; boost::prim_minimum_spanning_tree( graph , boost::make_associative_property_map< std::map<Vertex,Vertex> >(vertex_map) ); However, when converting boost::make_associative_property_map to a function object, the following code: std::map<Vertex,Vertex> vertex_map; boost::bind( boost_make_associative_property_map , vertex_map ) map_maker; boost::prim_minimum_spanning_tree( graph , map_maker() ); will not compile. The correct code is: std::map<Vertex,Vertex> vertex_map; boost::bind( boost_make_associative_property_map< std::map<Vertex,Vertex> > , vertex_map ) map_maker; boost::prim_minimum_spanning_tree( graph , map_maker() ); It took me quite a while to realize a mistake I made like this. I'm sure others will commit the same sort of mistake as well. Would it be too much for the Boost.Bind documentation to provide a note of caution with regard to function templates? Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Re: [boost] Re: compressed_pair requirements?
by JOAQUIN LOPEZ MU?Z 27 May '05

27 May '05

----- Mensaje original ----- De: Peter Dimov <pdimov(a)mmltd.net> Fecha: Viernes, Mayo 27, 2005 7:47 pm Asunto: Re: [boost] Re: compressed_pair requirements? > Howard Hinnant wrote: > > > 2. Uninitialized is better because it is much faster, > especially if > > you have containers of such elements. You can always explicitly > > initialize if you want. > > Technically... you can't put an uninitialized (non-character) > scalar in a > container; copying an uninitialized scalar is undefined behavior. > A similar issue also renders the following snippet illegal (unless someone has filed a DR): typedef set<int> int_set; pair<int_set::iterator,int_set::iterator> p; According to 20.2.2.2, the default ctor of std::pair works as if implemented like pair():first(int_set::iterator()),second(int_set::iterator()){} and int_set::iterator(), being a singular value, cannot be copied. A technical nitpick save for the fact that I actually was once static asserted by an overzealous checked STL implementation (don't remember which, I think it was Comeau). IMHO, std::pair default ctor should be defined as pair():first(),second(){} Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[property_map] Template parameter disorder
by Cromwell Enage 27 May '05

27 May '05

According to <http://www.boost.org/libs/property_map/iterator_property_map.html>, ValueType and IndexMap should be the third and second template parameters, respectively. Should <boost/property_map.hpp> be fixed to match its documentation? Cromwell D. Enage __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

[test lib] request for new features
by Thorsten Ottosen 27 May '05

27 May '05

Hi Gennadiy, I would like to see these functions added to the test library: BOOST_CHECK_NOT_EQUAL(x,y) BOOST_CHECK_NOT_CLOSE(x,y) and any similar functions that makes sense. I don't see how we can get the variables printed in the failed test without these functions. Thanks 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/

3 7

build from cvs, what is ICU_PATH?
by Neal Becker 27 May '05

27 May '05

I'm trying to build from cvs on Linux. Here's what I get: PYTHON_ROOT=/usr PYTHON_VERSION=2.4 bjam -sTOOLS=gcc stage ****************************************************** Building Boost.Regex with Unicode/ICU support disabled. HINT: define the environment variable ICU_PATH to point to the root directy of your ICU installation if you have one. Couldn't find utypes.h in ****************************************************** locate utypes.h /usr/include/schily/utypes.h Is this what it wants? How to I use it?

3 2

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Loïc Joly > Sent: Thursday, May 26, 2005 2:23 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Customer Friendlier Boost Installation > > Paul A Bristow a écrit : > > > Recently we had a flurry of discussion of why Boost is not more > widely used. > > > > I have used some bits of Boost happily for years, but recently I felt > I had > > to use it 'properly' so concluded it was time I used the bjam build > system - > > something I had felt looked a bit clever. > > > > > <SNIP> > > * Finally, installing boost takes longer than installing VC++... Is > building from the source such an important point ? Would'nt it be > possible to provide pre-built libraries for the 3 or 4 main compilers on > windows with each release ? The whole package, zipped, is 80mb on my VC8. > > -- > Loïc [Brian Braatz Writes:] Thank you for also suggesting that. Somewhere, someplace, an angel just got his wings.. :)

2 1

Requests for changes in 1.33 related to serialization
by Neal Becker 27 May '05

27 May '05

I want to suggest 2 changes that would be helpful at least to me, that relate to serialization. I use serialization with mersenne_twister and python. To support this 2 changes are needed: 1) serialization must be build as a shared library. I know this doesn't work on all platforms, but I believe it works on at least some, and therefore should be supported. 2) Please add support for serialization to mersenne_twister.hpp. All that's needed is this: template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & x; ar & i; }

6 9

Re: [Windows MSI Installer] - Using WIX
by Peter Foley 27 May '05

27 May '05

Hi, To be perfectly honest I haven't really looked for anything else and unless people can come up with a reason for not using WIX it is likely the one I will use. Why? Mainly for 2 reasons: 1. This is the one I am most familiar with (ie been reading about it for a long time) 2. I have been meaning for a long time to actually try using WIX. I guess this is my chance =p. Now does this mean it is the right tool to use for Boost? Hell no!!! But as I said unless there are good reasons for not using it I will probably just stick with this one. Although if other people have already started something else I am happy to contribute =p. Peter. ""Lars Gullik Bjønnes"" <larsbj(a)gullik.net> wrote in message news:<m3mzqh6je5.fsf(a)tyfon.gullik.net>... > "Peter Foley" <pjfoley(a)bigpond.com> writes: > > | Hi, > | > | I am in the process of looking at how feasible it would be to use WIX to > | create an MSI installer package for Boost for the Windows Platform(s). > | > | Now bearing in mind that I have never used WIX before and have been out of > | the programming game for a while I think I would like to help/run with this > | task. > > I know that several Open Source projects use the NSIS installer. > > You should perhaps have a look on that one as well. > > http://nsis.sourceforge.net/ > > -- > Lgb > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0

Re: [Windows MSI Installer] - Using WIX
by Peter Foley 27 May '05

27 May '05

Hi David, Comments inline. "David Abrahams" <dave(a)boost-consulting.com> wrote in message news:<ufyw9c5qm.fsf(a)boost-consulting.com>... > "Peter Foley" <pjfoley(a)bigpond.com> writes: [SNIP ...] > > * Install boost using an installer application > > * Detect necessary installation information > > * Provide "header only install" or header and lib file install" > > * Install foo library and dependencies and that is it > > * Configure various IDE's to support using boost > > * Install and register an MSDN Library of the boost documentation > > Did you miss my list or did you dislike everything on it? > http://article.gmane.org/gmane.comp.lib.boost.devel/124787 No I didn't miss it, I receive the list in Digest mode which makes it hard to find stuff sometimes (especially with this thread 150 replies). That list I created was from memory I am happy to incorporate your suggestions. [SNIP ...] > > > 1. Can we write a program that could work out if a library is header > > only? (generating a list of all these files) > > What do you mean by "work out?" Oh, I think you mean "decide." At > first I thought you meant "function properly." > > Yes, we can. What I am driving at is could we create a script/tool that would generate a list detailing these files and write it to a file that can be easily re-interpreted (ie output in XML or structured text). Maybe something like: [Library Name] [File Name] Foo Library foo.hpp During the build process this file will be read and incorporated into an XML document that the Candle (WIX Compiler) and then Light (WIX Linker) will generate the MSI from. > > > 2. Can we write a program that could work out if a library needs to be > > compiled as a lib file? (generating a list of all these files) > > Isn't that just the inverse of question 1? I guess so =p. Thinking about it the same tool described above could include this information. So modifying the Columns: [Library Name] [Header Only] [File Name] Foo Library YES bar.hpp The output will obviously be more complicated then this (to build the library you need the Jam file and anything else you usually would need). > > > 3. Can we write a program that could work out the dependencies between > > different libraries? (generating a list of all the dependencies) > > bcp I have not used bcp so excuse my ignorance if it already can do this. Can you configure it to run across the whole boost source tree and spit out an easily re-interpreted file listing the dependencies between all libraries? > > > 4. Is there a number of files that you would consider to be core boost > > files (ie something that the majority of boost libraries/users would use)? > > Yes, but why does that matter? If we allow people to limit how much > they install, they'll be offended if they get something they don't > need, even when it's in the "core." I guess I need to elaborate here. This isn't necessarily for the end users this is to hopefully simplify the dependency graph. Ie I am guessing a majority of libraries would use smart_ptr? Are there other libraries like this? To give you an indication on how I think an end user would use the installer (bare in mind this is pie in the sky stuff till I find out if it is possible =p) 1. Download MSI package from boost website, which will include - Bjam (pre-built) (zipped currently 83k) - Boost Sources (zipped currently 19MB) 2. Run the MSI and follow the bouncing ball (note this is not set in stone, just an idea of how I would love to see it) - View the boost License file(?) - Check for various Toolsets - Choose parts of boost to install, broken down by: (Note: Would need dependency information to break it down to this level) * Header Only libraries + Header A + Header B + Header C + Header D * Compiled libraries + Lib A + Lib B + Lib C + Lib D * Documentation + All (Default) + Selected header/lib's documentation * Rest of the support files needed for boost development (At a minimum I would default the installation to Headers, All documentation. But this is open to discussion and would be easy to chop and change) - Choose boost installation location - Choose the toolset - (Display if compiling lib's) Configure any additional options Bjam would use - Display a summary of the tasks about to be preformed 3. Once they click on finish the installer will - Extract the Header files and documentation to install directory - Invoke the command line and run the Bjam command to create the lib files - Update the toolset to use the boost files As long as everything works out the process to create a new MSI file for a new boost version for windows would be: 0. Get the stable boost branch from CVS 1. Generate header/lib XML file 2. Generate dependencies list 3. Process these files into the WIX XML document 4. Compile the WIX XML document 5. Link the WIX object files 6. Upload MSI Package to sourceforge This could be down by Script, Bjam, Make or by hand. Peter.

1 0

RE: [boost] Re: Wave Bjam building problems\Joel de Guzman-didyoueverfind a solution?
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Hartmut Kaiser > Sent: Thursday, May 26, 2005 9:58 AM > To: boost(a)lists.boost.org > Subject: RE: [boost] Re: Wave Bjam building problems\Joel de Guzman- > didyoueverfind a solution? > > > David Abrahams wrote: > > > > I am now trying to build the quick start with the VC71 IDE > > > > > > My current problem is this link error: > > > Linking... > > > LINK : fatal error LNK1104: cannot open file > > > 'libboost_wave-vc7-mt-gd-1_32.lib' > > > > > > Build log was saved at > > > > > "file://c:\data\Irx\Irx\Arx\Main\Source\Common\Boost\V_1_32\libs\wave\ > > > sa > > > mples\quick_start\Debug\BuildLog.htm" > > > WaveQuickStart - 1 error(s), 0 warning(s) > > > > > > > > > The LIB I have available is 'libboost_wave-vc71-mt-gd-1_32.lib not > > > 'libboost_wave-vc7-mt-gd-1_32.lib'. I am not sure WHY the > > autolinking > > > is trying to hit the vc70 version of the lib since I am > > using VC71's IDE. > > > > > > (ANYONE HAVE ANY SUGGESTIONS?) > > > > I don't know; this looks like a possible misuse of the > > autolink system by Wave, or... maybe you need to > > force-rebuild your entire vc71 project? If you have any > > object files lying around that were build with vc70 you'll > > have the incorrect autolink references in them. > > Wave uses the autolink feature as described in the docs. No misuse here, > at > least I'm not aware of such. > > Regards Hartmut [Brian Braatz Writes:] I am using VC71 IDE, it is trying to link against the VC70 lib (yes? Look at the name) A bjam build of quickstart did not work for me. I deleted VC70 from my box, removed it from everything, and deleted all the Objs generated everywhere and I got things to compile. But I am not linking yet. I am flying today but will be working on this more over the weekend. I plan on re-building a fresh machine, installing the compiler and boost and going at it fresh (unless someone comes up with a better idea :) ) THANKS FOR YOUR HELP. Sincerely, "The Village Idiot" "Beware the fury of a patient man" - John Dryden

1 0

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Rene Rivera > > Try this one... Gets you a good part of the way there.. > > http://boost-sandbox.sourceforge.net/boost-cvs-setup.exe > > [Brian Braatz Writes:] Allow me to also suggest an environment similar to Cgywin's. I have done this internal to our company and it has saved major problems in getting builds to actually work. If you find this interesting, I can attempt to explain it more.

1 0

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Rene Rivera > > Arkadiy Vertleyb wrote: > > "David Abrahams" <dave(a)boost-consulting.com> wrote in message > > news:uzmuit3q9.fsf@boost-consulting.com... > > > >>Jonathan Wakely <cow(a)compsoc.man.ac.uk> writes: > >> > >>> DON'T PANIC > >>> > >>>How about this? Worked for the best-selling book in the galaxy ;) > >> > >>I like it. Always good to start an adventure with a smile ;-) > > > > > > It's really not about command line versus GUI. It's just that default > > installation _should_ be one-button (or one batch command) operation. > > > > Instead, a simple requirement "install the quickbook" forses a person > to: > > > > 1) check out Boost CVS; > > 2) build bjam; > > 3) figure out the difference between Boost.Build v1 and v2; > > 4) download and configire Boost.Build v2; > > 5) figure out how to build the quickbook (any info about this in the > docs?) > > 6) download xslt processor from cygwin; > > 7) build the Boost.Book > > 8) Do whatever else (I am not even close to this right now). > > > > Sorry if I am somwhat off topic. Just waisting my day off, and being > > frustrated RIGHT NOW. > > Try this one... Gets you a good part of the way there.. > > http://boost-sandbox.sourceforge.net/boost-cvs-setup.exe > > [Brian Braatz Writes:] THIS COMPLETELY ROCKS! Please finish it. REQUEST: (ok, get ready to attack me) Install PreBuilt LIB files I would still cannot build wave and will be spending a chunk of the weekend working on this, if the install came with pre-built libs, I would have been able to have been coding for the 8 hours I have spent trying to get wave to work

1 0

RE: [boost] Re: Customer Friendlier Boost Installation
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Jeff Flinn > Sent: Thursday, May 26, 2005 9:29 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Customer Friendlier Boost Installation > > > "David Abrahams" <dave(a)boost-consulting.com> wrote in message > news:uzmui3mya.fsf@boost-consulting.com... > > "Jeff Flinn" <TriumphSprint2000(a)hotmail.com> writes: > > > >> Something like this as a start? > >> > >> For MSVC > >> ======== > >> > >> Organizing boost files > >> ====================== > >> > >> 1) Create a main boost directory which will contain the current and > >> future > >> boost library verstions. For example: C:\boost > > > > Maybe not such a good choice considering that it's the default install > > location for Windows? Or should we change the default (and if so, to > > what?) > > Sorry, "location for Windows" has too many overloads for me to know what > your asking here. What exactly is the problem using C:\boost? > [Brian Braatz Writes:] An idea to add to the mix. I config manage boost internal to my company- How I do that is I put boost into an internal CVS server I then make dirs (in CVS) like so Common\source\boost\v_1_32\ (boost distro goes here) This has an interesting effect of forcing the MSVC IDE project files to have "boost\v_1_32" embedded in a string in them. This allows me to keep 2 versions of boost side by side, and quickly (by changing the "Include directories path" setting in the IDE to test with different versions of boost I am going to be adding a Common\source\boost\Live\ at somepoint to be able to test off of current stuff - the difficult with that will be just scripting the CVS get from source forge, removing the cvs files added, and then re-adding to our internal cvs (and cvs does not support recursive add).

1 0

RE: [boost] Re: Wave Bjam building problems\Joel de Guzman -didyoueverfind a solution?
by Brian Braatz 27 May '05

27 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of David Abrahams > Sent: Thursday, May 26, 2005 8:48 AM > To: boost(a)lists.boost.org > Subject: [boost] Re: Wave Bjam building problems\Joel de Guzman - > didyoueverfind a solution? > > "Brian Braatz" <brianb(a)rmtg.com> writes: > > > Hartmut- HI THERE! > > I must say, I am excited to get the build fun over with so I can use > > your extremely cool creation. > > > > Details: > > I am using V2. I am NOW much closer. I am compiling but NOT LINKING- > > I have removed VC70 COMPLETELY from my box > > That was unneccessary. Sorry you did it. > > > and rebuilt boost with 71 > > (again). > > That an a using msvc : 7.1. : (path to cl.exe) in the user-config.jam > > got me to compile. > > > > Additionally, I went through and manually removed all of the references > > in my LIB, INCLUDE and PATH to vc70. > > Also unneccessary. > > > This may sound extreme, but it allowed BJAM to compile (Bjam's > > interaction with those ENV vars is something I don't fully know how it > > works) > > It doesn't interact with them. > > > I am now trying to build the quick start with the VC71 IDE > > > > My current problem is this link error: > > Linking... > > LINK : fatal error LNK1104: cannot open file > > 'libboost_wave-vc7-mt-gd-1_32.lib' > > > > Build log was saved at > > "file://c:\data\Irx\Irx\Arx\Main\Source\Common\Boost\V_1_32\libs\wave\sa > > mples\quick_start\Debug\BuildLog.htm" > > WaveQuickStart - 1 error(s), 0 warning(s) > > > > > > The LIB I have available is 'libboost_wave-vc71-mt-gd-1_32.lib not > > 'libboost_wave-vc7-mt-gd-1_32.lib'. I am not sure WHY the autolinking is > > trying to hit the vc70 version of the lib since I am using VC71's IDE. > > > > (ANYONE HAVE ANY SUGGESTIONS?) > > I don't know; this looks like a possible misuse of the autolink > system by Wave, or... maybe you need to force-rebuild your entire vc71 > project? If you have any object files lying around that were build > with vc70 you'll have the incorrect autolink references in them. > [Brian Braatz Writes:] Thanks for the notes. I am trying to get Wave working because I have a theory it could be useful to me for an instrument tool I envision adding to the proposed profiler. I am traveling today, but over the weekend, I am going to play with this some more. I am thinking about rebuilding a separate machine, and starting over from scratch (just to remove any weirdness in config I have on my main laptop).

1 0

[filesystem] WIN32 Can not use drive name in directory
by David Daeschler 27 May '05

27 May '05

Hello, >From my application there may come a time when I want to take a directory or file name from a user. In windows, there is a file selection box that can return the full path of a file that the user chooses. The full path in windows includes the drive name with a colon and then a backslash ( c:\ ). I can not seem to get the boost filesystem library to accept this as a valid path even with the native checker. I also ran the test provided with boost for paths and it failed. The output is given below. $ bfs Platform is Windows initial_path().string() is "g:/boostfs" initial_path().native_file_string() is "g:\boostfs" d:/srcbuilds/boost_1_32_0/boost/test/minimal.hpp(129): exception "std::exception : boost::filesystem::path: invalid name "c:" in path: "c:/"" caught in function: 'int main(int, char**)' **** Testing aborted. **** 1 error detected It appears that the colon is in the list of invalid characters for a file and it is throwing things off. My version of Boost was compiled with MinGW under Windows XP SP2 using the command line bjam "-sTOOLS=mingw" stage If I am missing something please let me know. Thank you for your time, - Dave

3 8

[Windows MSI Installer] - Using WIX
by Peter Foley 27 May '05

27 May '05

Hi, I am in the process of looking at how feasible it would be to use WIX to create an MSI installer package for Boost for the Windows Platform(s). Now bearing in mind that I have never used WIX before and have been out of the programming game for a while I think I would like to help/run with this task. >From lurking on the list for a while and also from the more recent "Customer Friendlier Boost Installation" thread here is a feature/wish list of items that I have seen or would personally like: * Install boost using an installer application * Detect necessary installation information * Provide "header only install" or header and lib file install" * Install foo library and dependencies and that is it * Configure various IDE's to support using boost * Install and register an MSDN Library of the boost documentation Obviously this list has some items on it that may not even be possible but hey we need something to aim for. Also the main goal would be to develop an automated rather then hand-rolic process for creating this MSI file. To help reach this goal I am hoping someone with more experience with the boost development process could shed some light on these questions. 1. Can we write a program that could work out if a library is header only? (generating a list of all these files) 2. Can we write a program that could work out if a library needs to be compiled as a lib file? (generating a list of all these files) 3. Can we write a program that could work out the dependencies between different libraries? (generating a list of all the dependencies) 4. Is there a number of files that you would consider to be core boost files (ie something that the majority of boost libraries/users would use)? Or if we cannot write a program to work it out how feasible would it be to have library maintainers maintain another file (for each library) containing this information? *ducks for cover* Seriously this file could be used for any platform to help with creating any form of installation package (RPMS, Debian Packages, whatever Darwin uses, ...) In effect if we could some how generate these files. We can then write a script that would create an XML file that the WIX application can convert into a useable MSI installation package automatically with virtually no user interaction (just need WIX and maybe the Windows Installer SDK installed). See this link for an example of how someone is doing an automated install build on windows: http://weblogs.asp.net/lorenh/archive/2004/05/09/128899.aspx?Pending=true With the finished tools/process I would almost hope it to be as simple as "Bjam package". Also the other main benefit with this would be all the files used to generate the MSI would be text files and can be checked into and out of CVS for version control. Thoughts? Peter. PS. Useful links for those who have never heard of WIX include: WIX Homepage: http://sourceforge.net/projects/wix/ Tutorial for WIX: http://www.tramontana.co.hu/wix/index.html

4 3

Using Boost.Book
by Arkadiy Vertleyb 27 May '05

27 May '05

The discussion about Boost.Build is valuable by itself, but OTOH, (why) do I need the Boost.Build to use the Boost.Book? Isn't Boost.Build just a way to run something that otherwise can be run from the command line? Regards, Arkadiy

2 2

[serialization] Another patch for Tru64
by Markus Schöpflin 27 May '05

27 May '05

Attached patch fixes a test failure on Tru64. As it could possibly affect other users of the RW library, I'm asking if anyone has any objections to this patch. Markus Index: remove_whitespace.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/archive/iterators/remove_whitespace.hpp,v retrieving revision 1.6 diff -u -r1.6 remove_whitespace.hpp --- remove_whitespace.hpp 27 Jan 2005 17:34:53 -0000 1.6 +++ remove_whitespace.hpp 25 May 2005 11:43:20 -0000 @@ -47,7 +47,8 @@ #endif #if defined(__STD_RWCOMPILER_H__) || defined(_RWSTD_VER) -// this is required for the RW STL on Linux: +// this is required for the RW STL on Linux and Tru64. +#undef isspace #undef iswspace #endif

2 2

Bowjlvuzgnwsfcajk
by mark.rodgers＠cadenza.co.nz 27 May '05

27 May '05

1 0

Re: Building boost for 64-bit on AIX [shared_ptr & single threading]
by Rene Rivera 26 May '05

26 May '05

Patrik Jonsson wrote: > Rene Rivera wrote: > >> Well that's a single threaded library, it would have "threading-multi" >> in the path if it was multi threaded. >> >>> ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_unlock >>> ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_lock >>> ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_init >>> ld: 0711-317 ERROR: Undefined symbol: .pthread_mutex_destroy >> >> >> >> It's likely that something other than Boost requires pthread. Could >> you find out what that is? It could be libstdc++, or something else.. >> > It seems to be that boost/greg_month.hpp includes boost/shared_ptr.hpp, > which uses boost/detail/shared_count.hpp which uses > /boost/detail/lightweight_mutex.hpp. The pthread symbols are in > greg_month.o, so it looks like that library won't work without threads > or else something's supposed to turn threads off but isn't working... Hmm... The only fix for this I can come up with is to add "<define>BOOST_LWM_USE_SPINLOCK", or probably more safely add "<linkflags>-pthread" to the BUILD. The current code, what's going to be 1.33, is rather different and is likely not to rely on pthreads on your platform. I think it uses native assembly in the GCC+PPC case. But more generally I would think that it should not generate *any* locking code when doing a single threaded build. I'm CC'ing the Boost list in the hope someone else can better resolve the problem. -- -- 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 2

how to build the quickbook?
by Arkadiy Vertleyb 26 May '05

26 May '05

Hi all, I just checked out the Boost CVS repository, and want to build the quickbook. However I can't find Jamfile there -- there is only Jamfile.v2. How should I build it? Thanks in advance, Arkadiy

3 3

[function_traits] Functions and function objects?
by Rene Rivera 26 May '05

26 May '05

The docs for function_traits.. http://www.boost.org/libs/type_traits/index.html#function_traits Don't mention if the traits work just for function types. Or if they will also work with function objects. Does it? -- -- 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

Upcoming lists.boost.org outage, FYI
by David Abrahams 26 May '05

26 May '05

-- Dave Abrahams Boost Consulting www.boost-consulting.com

1 0

Re: Microsoft Pragma(lib) decls (was RE: [boost] Customer Friendlier Boost Installation)
by Victor A. Wagner Jr. 26 May '05

26 May '05

At 11:08 2005-05-26, Bennett, Patrick wrote: > > -----Original Message----- > > From: boost-bounces(a)lists.boost.org >[mailto:boost-bounces@lists.boost.org] > > On Behalf Of Victor A. Wagner Jr. [deleted] > > >in with users having no idea how or why they're being linked against. > > >Since many developers tend to be rather over-eager in #including >headers > > >(bah, just include it all!) > > > > sounds like "many developers" need to be re-edcuated. or, perhaps, >you > > need better code walkthroughs. > >[Bennett, Patrick] Both. :) That doesn't change the fact that having >object files which contain special decorations (inserted by a >vendor-specific #pragma operation) that's twice in 2 days that someone wants to pick on #pragma being "vendor specific" I never suggested either time a literal "#pragma blah" to support this. >which cause unspecified libraries to >'automatically' get linked in is a 'bad thing.' >For one, there's no official way to dump a list of these explicit link >references for any given object file or lib/dll. were the mechanism part of the standard, of course there would be an "official" way to find them >The only way to (partially) know what might get linked in ahead of time >is to go through a dedicated preprocessor step to verify what's being >linked. Of course, this just handles the case where the public >(interface) headers of all libraries referenced contain pragma/lib >entries. It doesn't account for the libraries which defined pragma/lib >entries for other libraries within their implementation headers [so the >pragma node is only in the linkable file for that static lib or dll's >import lib]. Thus, there's no way to 'know' up-front, and in an >easy/fast manner, what libraries will actually be linked in when >building a dll or exe in the presence of these lib pragma's. They're >bad, bad, bad. you assumed things I didn't suggest. >Vendors like Microsoft are certainly welcome to support them, but adding >something like this to the 'standard' would be unacceptable (to me at >least ;>). If tool authors want to provide support for Microsoft's >extension, that's fine too - it should just always be optional. > >When it comes to compiling and linking, I don't want the compiler or >linker including anything more than I explicitly told it to include. > >If you disagree, well, hey, I guess we'll just have to agree to >disagree. no, I'm gonna convince you, lol. >Cheers... >Patrick Bennett Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

Microsoft Pragma(lib) decls (was RE: [boost] Customer Friendlier Boost Installation)
by Bennett, Patrick 26 May '05

26 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Victor A. Wagner Jr. > Sent: Wednesday, May 25, 2005 10:34 PM > To: boost(a)lists.boost.org > Subject: RE: [boost] Customer Friendlier Boost Installation > > At 14:30 2005-05-25, Bennett, Patrick wrote: > >[delete] > >[Bennett, Patrick] Personally, I think the pragma 'link' options are an > >absolute disaster for large projects. > > apparently you've worked with different folks than I. Likely, different > kinds of "large projects", too. [Bennett, Patrick] Well, a single full build is over 55 GB. To me at least, that's large. :) > >It's far, far too easy to end up with lots of libraries getting linked > >in with users having no idea how or why they're being linked against. > >Since many developers tend to be rather over-eager in #including headers > >(bah, just include it all!) > > sounds like "many developers" need to be re-edcuated. or, perhaps, you > need better code walkthroughs. [Bennett, Patrick] Both. :) That doesn't change the fact that having object files which contain special decorations (inserted by a vendor-specific #pragma operation) which cause unspecified libraries to 'automatically' get linked in is a 'bad thing.' For one, there's no official way to dump a list of these explicit link references for any given object file or lib/dll. The only way to (partially) know what might get linked in ahead of time is to go through a dedicated preprocessor step to verify what's being linked. Of course, this just handles the case where the public (interface) headers of all libraries referenced contain pragma/lib entries. It doesn't account for the libraries which defined pragma/lib entries for other libraries within their implementation headers [so the pragma node is only in the linkable file for that static lib or dll's import lib]. Thus, there's no way to 'know' up-front, and in an easy/fast manner, what libraries will actually be linked in when building a dll or exe in the presence of these lib pragma's. They're bad, bad, bad. Vendors like Microsoft are certainly welcome to support them, but adding something like this to the 'standard' would be unacceptable (to me at least ;>). If tool authors want to provide support for Microsoft's extension, that's fine too - it should just always be optional. When it comes to compiling and linking, I don't want the compiler or linker including anything more than I explicitly told it to include. If you disagree, well, hey, I guess we'll just have to agree to disagree. Cheers... Patrick Bennett

2 1

RE: [boost] Wave Bjam building problems\Joel de Guzman -did youeverfind a solution?
by Brian Braatz 26 May '05

26 May '05

Hartmut- HI THERE! I must say, I am excited to get the build fun over with so I can use your extremely cool creation. Details: I am using V2. I am NOW much closer. I am compiling but NOT LINKING- I have removed VC70 COMPLETELY from my box and rebuilt boost with 71 (again). That an a using msvc : 7.1. : (path to cl.exe) in the user-config.jam got me to compile. Additionally, I went through and manually removed all of the references in my LIB, INCLUDE and PATH to vc70. This may sound extreme, but it allowed BJAM to compile (Bjam's interaction with those ENV vars is something I don't fully know how it works) I am now trying to build the quick start with the VC71 IDE My current problem is this link error: Linking... LINK : fatal error LNK1104: cannot open file 'libboost_wave-vc7-mt-gd-1_32.lib' Build log was saved at "file://c:\data\Irx\Irx\Arx\Main\Source\Common\Boost\V_1_32\libs\wave\sa mples\quick_start\Debug\BuildLog.htm" WaveQuickStart - 1 error(s), 0 warning(s) The LIB I have available is 'libboost_wave-vc71-mt-gd-1_32.lib not 'libboost_wave-vc7-mt-gd-1_32.lib'. I am not sure WHY the autolinking is trying to hit the vc70 version of the lib since I am using VC71's IDE. (ANYONE HAVE ANY SUGGESTIONS?) Additionally, I will try your suggestion below just to see what happens. THANK YOU Brian Braatz Info and tips for anyone who might find this mail in the archives: 1- Try to build the spirit example FIRST, if you cant build the examples with Spirit, you will not be able to get wave to compile 2- Remove all the references to other compilers in LIB, INCLUDE and PATH, this seemed to clean things up for me (though this SHOULD not be necessary I believe) 3- Maintain patience and perseverance. :) > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Hartmut Kaiser > Sent: Thursday, May 26, 2005 5:20 AM > To: boost(a)lists.boost.org > Subject: RE: [boost] Wave Bjam building problems\Joel de Guzman -did > youeverfind a solution? > > > Brian, > > IIRC, removing the /GR switch (generate RTTI) should solve the problem. > > But the Wave jamfiles in the Boost CVS:HEAD should work fine, didn't they? > Anyway, I'll retry to compile it today based on the Boost 1.32 release. > > Are you using Build V1 or V2? Joel reported the error went away after > switching to the V1 Jamfiles. > > Regards Hartmut > > > > Attempting to BUILD WAVE, I have spent the last few hours > > (midnight til > > 5am) searching the archives and trying different things. ( > > the below email is the exact problem I am having) > > > > I have tried both the review version of wave and the one in > > CVS applied to the 1.32 release. I am using vc7.1 > > > > Has anyone found the issue below yet? > > > > Many thanks, > > > > Brian > > > > > > > -----Original Message----- > > > From: boost-bounces(a)lists.boost.org > > [mailto:boost-bounces@lists.boost.org] > > > On Behalf Of Joel de Guzman > > > Sent: Sunday, February 13, 2005 2:55 PM > > > To: boost(a)lists.boost.org > > > Subject: [boost] Re: Wave review > > > > > > Hartmut Kaiser wrote: > > > > > > > > Joel de Guzman wrote: > > > > > > > >>+ when using bjam V2, VC7.1 fails with a buffer overrun > > (compiler > > > >> problem). No problem with bjam V1. I wanted to try > > the samples > > > >> but they don't have a V1 Jamfile, only V2. So I had to switch > > > >> to using g++ instead. So far so good. > > > > > > > > > > > > Sure they have, haven't they? I'm pretty sure that I've added V1 > > > Jamfile's. > > > > But thanks for reporting the V2 problems. Please add the line > > > > > > > > : <toolset>vc-7_1:<rtti>off # workaround for > > compiler bug > > > > > > > > to the V2 Jamfile's, without that VC7.1 simply fails - please look > > at > > > the V2 > > > > Jamfile of the library itself for a sample > > > > ($BOOST_ROOT/libs/wave/build/Jamfile.v2). > > > > > > Hi Hartmut, > > > > > > VC7.1 still bombs with "buffer overrun". Here's the bjam output: > > > > > > C:\dev\boost\libs\wave\build>bjam --v2 ...found 108 targets... > > > ...updating 5 targets... > > > msvc.compile.c++ > > > ..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiate_cpp_gram > > > mar.obj > > > instantiate_cpp_grammar.cpp > > > > > > call "C:\Program Files\Microsoft Visual Studio .NET > > > 2003\Vc7\bin\vcvars32.ba t" > nul cl /Zm800 -nologo -TP > > > -DBOOST_ALL_NO_LIB=1 /Z7 /Od /Ob0 /EHsc /GR > > > /MDd -I"C > > > :\dev\boost" -c > > > -Fo"..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiate_cpp_ > > > grammar.obj" "..\src\instantiate_cpp_grammar.cpp" > > > > > > ...failed msvc.compile.c++ > > > ..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiat > > > e_cpp_grammar.obj... > > > > > > Did I do something wrong? > > > > > > -- > > > Joel de Guzman > > > http://www.boost-consulting.com > > > http://spirit.sf.net > > > > > > _______________________________________________ > > > Unsubscribe & other changes: > > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

3 3

Re: Customer Friendlier Boost Installation
by Peter 26 May '05

26 May '05

[De-Cloak] I have been reading this thread with interest. I thought I would throw my comments in regarding making the installation a little bit easier. Since I also had issues following the instructions. ------------------------------ Message: 7 Date: Wed, 25 May 2005 19:18:46 -0400 From: David Abrahams <dave(a)boost-consulting.com> Subject: [boost] Re: Customer Friendlier Boost Installation To: boost(a)lists.boost.org Message-ID: <ubr6y51yh.fsf(a)boost-consulting.com> Content-Type: text/plain; charset=us-ascii Caleb Epstein <caleb.epstein(a)gmail.com> writes: > Admittedly there should be example command lines for vc-7_1 etc and > not just gcc. Can you suggest where we should show those examples? There are quite a few toolsets! Maybe in the table? -- Dave Abrahams Boost Consulting www.boost-consulting.com ------------------------------ Hmm, is this a case of not seeing the forest because of the trees? Why use static content in this instance at all? If you really want to simplify it why not use some sort of applet? We are programmers after all =p (well I am trying to be) Ie, on the Getting started page have a "Generate Bjam command line" link, on this page the user just selects: * Compiler (Drop down list) * Optional command line switches (Check boxes, with links to what each item does) - Optional path to Python if it is getting built * Path to extracted source of boost (Defaults to c:\Temp\Boost) * Path to compiled version of boost (Defaults to c:\Boost) User clicks on submit and it presents the correct command line command. User cuts and pastes this on a command prompt they hit enter and away they go. Obviously they still need to worry about the environment variables pointing to the compiler and linker and such. For bonus points extend bjam for "bjam -check_Env gcc". This will spit out an OK message listing the env variables it recognises. It will also spit out messages for env variables that it needs but cannot find. Ie, user would run "Bjam - check_env gcc" or "Bjam -check_env CW" and so on. (once again could be part of the generate bjam command line command weblink. This should also be fairly simple to maintain if the applet gets the compilers list (and env variables/or specific exe's it is looking for) from an easily updated list that can be updated as new compiler versions or differences come out. I guess the only thing stopping this is the capabilities of the web server and finding someone who is happy to extend Bjam and write the applet. Then the process for install (with no other modifications would be): 1. Download boost source and extract 2. Download Bjam and extract 3. Run "Bjam - Check_Env" and fix any environment variable issues 4. Generate Bjam command line command from website (or from application?) and run it. 5. Update Include files path and lib file path in your favourite IDE, Make Files, ... Also keep the online documentation for those who are happy to learn about the intricacies of using Bjam. What do you think? Peter. PS I could have actually just walked straight into that tree in the forst and just be seeing stars =p

2 1

RE: [boost] Re: Re: Customer Friendlier Boost Installation
by Brian Braatz 26 May '05

26 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Hendrik Schober > > We are using more than two dozen 3rd-party SDKs and > libraries, both free software and commercial ones, > some across almost half a dozen platforms. We are > using boost since 2001. > > I have never written an MFC app. Not a single one. > (Of a dozen or so developers here, I know one who > has for some toy projects.) > > I am considered the "C++ expert" here and people > often are annoyed that I am forcing them to learn > where 'typename' is required, how template template > parameters are working, and what these 4k error > messages from template meta code mean. :^> (I would > suppose everyone here knows what virtual bases are > for.) > > I have failed to build/install boost without > putting considerably more effort into it than I > needed to put into many other libraries. That is, I > was unable to just download it and check it out. > I think this would be the same with most Win/Mac > developers here. > > > /David Bergman [Brian Braatz Writes:] Yes I understand where you are coming from. And if everything remains the same, Boost will only be available for people capable of doing this. The difficulty here, in my humble opinion, is the simple fact that this list has *extremely* smart people on it. This is great, but a difficulty with *extremely* smart people, is if THEY have an easy time of something they tend to loose sight of that being difficult for someone else. Boosters can choose to expend zero effort on this thinking. All it will mean is much less people will be exposed to boost. (that's too bad) I take my position with great authority and experience. Dare I say that my qualifications in this area far exceed the average booster. I, unlike the major of you, exist as a complete and total idiot. :) "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. " Albert Einstein

1 0

[signals] bug in named_slot_map.hpp ?
by Christophe Prud'homme 26 May '05

26 May '05

Dear boosters, line 103 of /cvsroot/boost/boost/boost/signals/detail/named_slot_map.hpp I believe it should be last_group(last) instead of last_group(group) If it is not the case then the argument last should be commented out to avoid "unused" warnings Best regards C. Index: named_slot_map.hpp =================================================================== RCS file: /cvsroot/boost/boost/boost/signals/detail/named_slot_map.hpp,v retrieving revision 1.8 diff -u -r1.8 named_slot_map.hpp --- named_slot_map.hpp 19 Apr 2005 13:50:53 -0000 1.8 +++ named_slot_map.hpp 25 May 2005 10:07:39 -0000 @@ -100,7 +100,7 @@ { init_next_group(); } named_slot_map_iterator(group_iterator group, group_iterator last, slot_pair_iterator slot) : - group(group), last_group(group), slot_(slot), slot_assigned(true) + group(group), last_group(last), slot_(slot), slot_assigned(true) { } void init_next_group() -- MIT Affiliate

3 2

Wave Bjam building problems\Joel de Guzman -did you ever find a solution?
by Brian Braatz 26 May '05

26 May '05

Attempting to BUILD WAVE, I have spent the last few hours (midnight til 5am) searching the archives and trying different things. ( the below email is the exact problem I am having) I have tried both the review version of wave and the one in CVS applied to the 1.32 release. I am using vc7.1 Has anyone found the issue below yet? Many thanks, Brian > -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Joel de Guzman > Sent: Sunday, February 13, 2005 2:55 PM > To: boost(a)lists.boost.org > Subject: [boost] Re: Wave review > > Hartmut Kaiser wrote: > > > > Joel de Guzman wrote: > > > >>+ when using bjam V2, VC7.1 fails with a buffer overrun (compiler > >> problem). No problem with bjam V1. I wanted to try the samples > >> but they don't have a V1 Jamfile, only V2. So I had to switch > >> to using g++ instead. So far so good. > > > > > > Sure they have, haven't they? I'm pretty sure that I've added V1 > Jamfile's. > > But thanks for reporting the V2 problems. Please add the line > > > > : <toolset>vc-7_1:<rtti>off # workaround for compiler bug > > > > to the V2 Jamfile's, without that VC7.1 simply fails - please look at > the V2 > > Jamfile of the library itself for a sample > > ($BOOST_ROOT/libs/wave/build/Jamfile.v2). > > Hi Hartmut, > > VC7.1 still bombs with "buffer overrun". Here's the bjam output: > > C:\dev\boost\libs\wave\build>bjam --v2 > ...found 108 targets... > ...updating 5 targets... > msvc.compile.c++ > ..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiate_cpp_gram > mar.obj > instantiate_cpp_grammar.cpp > > call "C:\Program Files\Microsoft Visual Studio .NET > 2003\Vc7\bin\vcvars32.ba > t" > nul > cl /Zm800 -nologo -TP -DBOOST_ALL_NO_LIB=1 /Z7 /Od /Ob0 /EHsc /GR > /MDd -I"C > :\dev\boost" -c > -Fo"..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiate_cpp_ > grammar.obj" "..\src\instantiate_cpp_grammar.cpp" > > ...failed msvc.compile.c++ > ..\..\..\bin.v2\libs\wave\build\msvc\debug\instantiat > e_cpp_grammar.obj... > > Did I do something wrong? > > -- > Joel de Guzman > http://www.boost-consulting.com > http://spirit.sf.net > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

misuse of BOOST_NO_INTRINSIC_WCHAR_T in boost/lexical_cast.hpp
by Bronek Kozicki 26 May '05

26 May '05

I believe that there is no reason why BOOST_NO_INTRINSIC_WCHAR_T should be taken into account when defining DISABLE_WIDE_CHAR_SUPPORT at the beginning of lexical_cast.hpp file. The fact that on some platform wchar_t is not builtin type (as it should be) but some typedef (e.g. to short), should not disable wchar_t support in lexical_cast. If platform does not have any support for wchar_t then other macros (e.g. BOOST_NO_STD_WSTRING) will be defined, leading to definition of DISABLE_WIDE_CHAR_SUPPORT. On the other hand, if some platform emulates wchar_t and has decent support for wide strings, wide streams etc, then there is no real reason to disable lexical_cast support for wchar_t on such platform. My coleague was just bitten by this when trying to use lexical_cast on MSVC6: >>>> citation begin Using Microsoft Visual Studio 6 and DinkumWare 2.3 Standard library, I was prevented from using lexical_cast with wide strings. The BOOST_NO_INTRINSIC_WCHAR_T was defined, which prevents the wide character parts of lexical_cast from being compiled. Reading the documentation on BOOST_NO_INTRINSIC_WCHAR_T, it would seem that this was not used appropriately in lexical_cast.hpp By removing the line from lexical_cast.hpp I was able to successfully compile and use lexcical_cast with wstring. Modified lexical_cast.hpp. In this section : #if defined(BOOST_NO_STRINGSTREAM) || \ defined(BOOST_NO_STD_WSTRING) || \ defined(BOOST_NO_STD_LOCALE) || \ defined(BOOST_NO_INTRINSIC_WCHAR_T) removed || \ defined(BOOST_NO_INTRINSIC_WCHAR_T) >>>> citation end I hope that our findings are correct and this can be fixed in release 1.33 . Regards B.

1 0

[iostreams] test/Jamfile.v2
by Vladimir Prus 26 May '05

26 May '05

Hi Jonathan, if I to to libs/iostreams/test and run "cvs log Jamfile.v2", I get this: revision 1.3 date: 2005/05/02 21:20:04; author: turkanis; state: dead; lines: +0 -0 obsolete What does that mean? The log message says next to nothing, and the file removal basically breaks my V2 testing. Not to mention that it took me a while to realize the file is removed in CVS. If you modified Jamfile in some way and did not want to update Jamfile.v2 (and you don't have to, until V2 is official), you could simply drop me a note. Or you could do nothing, since as soon as I'll do another V1 vs. V2 test results comparison I'll see the difference and update Jamfile.v2 myself. Where there any specific reason for removal? - Volodya

2 2

RE: [boost] Customer Friendlier Boost Installation
by Victor A. Wagner Jr. 26 May '05

26 May '05

At 14:30 2005-05-25, Bennett, Patrick wrote: >[delete] >[Bennett, Patrick] Personally, I think the pragma 'link' options are an >absolute disaster for large projects. apparently you've worked with different folks than I. Likely, different kinds of "large projects", too. >It's far, far too easy to end up with lots of libraries getting linked >in with users having no idea how or why they're being linked against. >Since many developers tend to be rather over-eager in #including headers >(bah, just include it all!) sounds like "many developers" need to be re-edcuated. or, perhaps, you need better code walkthroughs. > it's quite common for library x to include >library y which happens to include library z. Users then wonder why >their application is suddenly dependent on libraries they never even >'use'. >Libraries linked against should always be completely explicit IMO yeah, I woulda bought that right up until Microsoft introduced incompatible options in their silly "see 8 things at a time" _GUI_ option settings (property pages). BTW, those are a perfect example of why I dislike GUI for most things, it gets abused horribly (yeah I know, let's just educate people how to write them correctly). > (or >managed by a build system that documents the dependencies). When the >linkage is explicit, the cases where libraries have too many >inter-dependencies (usually incorrect) tend to get fixed pretty quickly. > >Patrick Bennett > > > >_______________________________________________ >Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

RE: [boost] Customer Friendlier Boost Installation
by Bennett, Patrick 25 May '05

25 May '05

> -----Original Message----- > From: boost-bounces(a)lists.boost.org [mailto:boost-bounces@lists.boost.org] > On Behalf Of Victor A. Wagner Jr. > Sent: Wednesday, May 25, 2005 3:42 PM > To: boost(a)lists.boost.org; boost(a)lists.boost.org > Subject: Re: [boost] Customer Friendlier Boost Installation > > At 04:13 2005-05-25, Stuart Dootson wrote: > >[deleted] > >One final point - whoever came up with the autolinking scheme (think > >it was John Maddock?) - thank you very much - that makes life *so* > >much easier! > > Yes, it does! > It's a wonder that the committee didn't insist long ago that there be a > directive in the language which would pass a name(file?) to the linker for > processing. It's not like we haven't been fighting this problem since the > late 1970s and it's still a compiler specific thing. Kinda makes you > wonder exactly what things the committee deems important, and why (we > STILL > don't have #pragma once as a "standard" requirement). [Bennett, Patrick] Personally, I think the pragma 'link' options are an absolute disaster for large projects. It's far, far too easy to end up with lots of libraries getting linked in with users having no idea how or why they're being linked against. Since many developers tend to be rather over-eager in #including headers (bah, just include it all!) it's quite common for library x to include library y which happens to include library z. Users then wonder why their application is suddenly dependent on libraries they never even 'use'. Libraries linked against should always be completely explicit IMO (or managed by a build system that documents the dependencies). When the linkage is explicit, the cases where libraries have too many inter-dependencies (usually incorrect) tend to get fixed pretty quickly. Patrick Bennett

1 0

Re: [boost] Re: [repost][serialization] autolinking
by JOAQUIN LOPEZ MU?Z 25 May '05

25 May '05

Hello Robert, ----- Mensaje original ----- De: Robert Ramey <ramey(a)rrsd.com> Fecha: Miércoles, Mayo 25, 2005 6:02 pm Asunto: [boost] Re: [repost][serialization] autolinking > Its not a policy that including serialization trigger autolinking. > If it > currently does, it contravenes my intention. When I last looked > at this I > wasn't convinced this was actually happening. I took precautions > to avoid > this and felt it was addressed. Your detailed investigation > motivates me to > look again and more carefully. It is also helpful for showing me > where to > look. I'll do this. Thanks for sheding light on this. > > I've been a little bogged down in this area as now the auto- > linking of DLLS > on vc6 and vc7 stopped working. I'm not sure why this is. Its > only a > problem on with these compilers. I'm still bogged down on this. > Good to know you're on it. If you need to do some fast testing on MSVC++ 6.0, I've got that environment available --just drop me a line and I'll try to lend a hand. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[test] Confusion about BOOST_CHECK_CLOSE
by Jody Hagins 25 May '05

25 May '05

I have re-read everything I can find about BOOST_CHECK_CLOSE, and the doc on floating point comparison algorithms (i.e.close_at_tolerance). However, I am still confused about how to use BOOST_CHECK_CLOSE. Could we have some clear examples of comparisons that pass/fail with different tolerance settings, and some explanation as to how changing the tolerance may affect the test? Currently, I have a test, using BOOST_CHECK_CLOSE() which passes, no matter how big/small I set the tolerance; yet the values are different. Thanks!

3 5

[repost][serialization] autolinking
by Joaquín Mª López Muñoz 25 May '05

25 May '05

Allow me to repost a digest of my last two messages about the issue of autolinking in Boost.Serialization. If the final decision is to *not* adhere to my proposed policy, I'd be grateful to know asap, so that I can hack my way in my own source code. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo ----------------------- I humbly request that you reconsider your design so that the following guarantee is honored: * (A) Any code including *only* boost/serialization/*.hpp headers won't trigger autolinking of Boost.Serialization. The following is a rationale for this policy: a 3rd party library that provides *intrusive* serialization capabilities will most likely need to include some of boost/serialization/*.hpp. If those headers trigger autolinking, the user will face the annoying fact that Boost.Serialization is autolinked even if she didn't explicitly try to use serialization at all. Granted, if the serialization capabilities of the 3rd party library are not taking advantge of, autolinking will ultimately have no effect on the final binary, but the point is that the user will be forced nonetheless to have the Boost.Serialization lib built and available. This is most unfortunate in the case the 3rd party library is a header-only lib, since the user may very well be using it without having built anything from Boost. This is exactly what's happening now with Boost.MultiIndex. Autolinking is triggered by the (implicit) inclusion of boost/serialization/config.hpp. This header is in turn included by void_cast.hpp and extended_type_info.hpp, and if you pull out from this thread it turns out virtually any boost/serialization/*.hpp header will trigger autolinking. To honor (A), you just have to remove the inclusion of boost/serialization/config.hpp by the aforementioned void_cast.hpp and extended_type_info.hpp. From what I can see, the inclusion is done so as to bring in the definition of BOOST_SERIALIZATION_DECL, so in principle having this macro defined in a separate header would suffice. If (A) is honored, autolinking will be triggered only when including boost/archive/*.hpp headers, which IMHO is just fine, since these are a sure sign that the user (not the 3rd party library) is explicitly requesting serialization capabilities and will welcome the autolinking stuff. I have inspected the source code and looks like autolinking is triggered in three points: boost/serialization/config.hpp boost/archive/detail/auto_link_archive.hpp boost/archive/detail/auto_link_warchive.hpp So, it seems like my proposal boils down to removing autolinking from the first header. As a proof of concept, I've done so (see attached modified source); with this changes in place, my local tests seem to indicate that: * Autolinking does not kick in if including only boost/serialization/*.hpp headers. * Autolinking still works if including any of boost/archive/*.hpp. boost/serialization/config.hpp has a local macro named IMPORT whose semantics escapes me, so I might be missing something.

2 1

RE: [boost] Re: Customer Friendlier Boost Installation
by Martin Bonner 25 May '05

25 May '05

----Original Message---- From: Jason Earl [mailto:Jason@hybd.net] Sent: 25 May 2005 14:37 To: boost(a)lists.boost.org Subject: Re: [boost] Re: Customer Friendlier Boost Installation > After all anyone with experience with > Unix will realise how much of an advantage a shell is So? What about the very large number of professional programmers who have no experience of Unix, and are too young to have had to wrestle the user-hostile environment that was the DOS command line. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

2 1

[Program options] Borland, VC7 failures?
by Doug Gregor 25 May '05

25 May '05

The majority of the program_options tests on these compilers are failing. I see that other similarly-broken configurations (VC6, VC6 with STLport) are marked unusable. Will program_options work on these compilers or should it be marked unusable? Doug

2 1

[integer] patch for MSVC++ 6.0
by Joaquín Mª López Muñoz 25 May '05

25 May '05

There's currently a test case for Boost.Integer failing in MSVC ++ 6.0 with a LNK1179 error: http://tinyurl.com/8rpuu This bug in MSVC++ 6.0 shows when the compiler emits different symbol names with a very long common prefix: in this particular case, the offending symbol names are generated by a couple of BOOST_CHECK instantiations. The proposed patch works around the problem and only affects to the test code, not the library, so I guess it's safe enough. OK to commit? Joaquín M López Muñoz Telefóinca, Investigación y Desarrollo 56a57,63 > #if defined(BOOST_MSVC) && (BOOST_MSVC <= 1200) > // MSVC++ 6.0 issues a LNK1179 error (duplicate comdat) when the compiler > // generates different symbol names with a very long common prefix: > // the dummy "&& true" disambiguates between the symbols generated by this > // BOOST_CHECK instantiation and the preceding one. > BOOST_CHECK(traits::is_integer && true); > #else 57a65 > #endif

2 1

[date_time] minor warning fix
by Christophe Prud'homme 25 May '05

25 May '05

Dear Booster I have attached a trivial patch for date_facet.hpp to avoid unnecessary warnings in date_facet.hpp with g++ -Wall/-Wunused Best regards C. -- Christophe Prud'homme Office MA B2 534 CMCS-IACS EPFL CH-1015 Lausanne, Switzerland Tel: +41 (0)21 693 25 47 Fax: +41 (0)21 693 43 03

2 1

Lambda just faild in VC8
by Victor A. Wagner Jr. 25 May '05

25 May '05

my latest run shows Lambda failing in trying to build (that old manifest again) the last part Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"

1 0

[Test library] wide_string test and wputenv
by Doug Gregor 25 May '05

25 May '05

The test library's wide_string tests are failing on any platform because "wputenv" does not exist. Googling around a bit, I don't see much mention at all of "wputenv". There is a _wputenv on Microsoft compilers, but it takes wchar_t pointers, not char pointers. This is part of a much larger problem... a quick count in the regression tests shows about 300 failures coming from the test library. Most of these are on compilers we usually consider rather broken, but we need someone to look at these failures and either fix them or mark them. The Boost.Test library is one of the core libraries, on which every other library depends. It needs to be solid, stable, and portable, or we cannot release 1.33.0. Doug Gregor 1.33.0 Release Manager

6 10

[1.33.0] Final destination for 1.33 test results?
by JOAQUIN LOPEZ MU?Z 24 May '05

24 May '05

index.htm as currently in the CVS has the following URL http://www.meta-comm.com/engineering/boost-regression/1_33_0/index.html under the name "Release". Currently, the link fails. Is this the stable URL where 1.33 final results will be stored? I'd like to include this in some of my docs and I guess I'll have to do it "blindly" i.e before the URL gets any actual contents, so I want to make sure. Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[test] Turning off signal traps
by Jody Hagins 24 May '05

24 May '05

I have a test that is failing, and I am using the auto tests... #define BOOST_AUTO_TEST_MAIN #include <boost/test/auto_unit_test.hpp> #include "foo.hpp" BOOST_AUTO_UNIT_TEST(blarg) { BOOST_CHECK_EQUAL(do_something(), 0); } However, somewhere a SEGV is happening. How can I turn off the test signal catching for this test so that I can get a core file for debugging?

2 1

Big Integer uploaded to sandbox, volunteer seeked for submission to boost
by christopher diggins 24 May '05

24 May '05

I just uploaded a very simple arbitrary precision unsigned integer class to the sandbox ( http://boost-sandbox.sourceforge.net/vault/index.php ). The class is implemented using naive algorithms and is based on std::vector<bool>. Efficiency was absolutely not a concern, the priority was placed on correctness. Without meaning to undermine the impressive work on the expression template big_integer class I thought perhaps programmers would generally prefer a more portable and quickly compiled class. The interface of the type I posted is: class big_uint { typedef big_uint self; public: big_uint(); big_uint(const self& x); big_uint(const std::vector<bool>& x); big_uint(int x); self& operator=(const std::vector<bool>& x); self& operator<<=(int n); self& operator>>=(int n); self operator++(int); self operator--(int); self& operator++(); self& operator--(); self& operator+=(const self& x); self& operator-=(const self& x); self& operator*=(self x); self& operator/=(const self& x); self& operator%=(const self& x); self operator~() const; self& operator&=(self x); self& operator|=(self x); self& operator^=(self x); bool operator[](int n) const; int size() const; unsigned long to_ulong(); friend self operator<<(const self& x, unsigned int n); friend self operator>>(const self& x, unsigned int n); friend self operator+(const self& x, const self& y); friend self operator-(const self& x, const self& y); friend self operator*(const self& x, const self& y); friend self operator/(const self& x, const self& y); friend self operator%(const self& x, const self& y); friend self operator^(const self& x, const self& y); friend self operator&(const self& x, const self& y); friend self operator|(const self& x, const self& y); friend bool operator==(const self& x, const self& y); friend bool operator!=(const self& x, const self& y); friend bool operator>(const self& x, const self& y); friend bool operator<(const self& x, const self& y); friend bool operator>=(const self& x, const self& y); friend bool operator<=(const self& x, const self& y); }; For acceptance into Boost I would guess that this class would have to be much more efficient (though my view is that something that works is better than nothing that runs fast). Unfortunately I can not spend any significant amount of time optimizing it nor doing a proper submission (I would not have time available until around August), so if someone would like to volunteer to take it over, I would appreciate it. Any comments would be most welcome. -- Christopher Diggins http://www.cdiggins.com

1 0

random.hpp - suggestion for utility function
by christopher diggins 24 May '05

24 May '05

AFAICT the shortest way to emulate the std::rand() function using boost/random.hpp would be as follows: unsigned int longhand_boost_rand() { boost::mt19937 rng; boost::uniform_int<> dist(0, RAND_MAX); boost::variate_generator < boost::mt19937, boost::uniform_int<> > generator(rng, dist); return generator(); } (apologies if I made any mistakes) I was wondering if there would be any reason not to provide a utility function which made it easier to write random number generators. For instance, the following: template<class Dist_T, class Rng_T> typename boost::variate_generator<Rng_T, Dist_T>::result_type generate_rand(Dist_T dist, Rng_T rng) { return boost::variate_generator<Rng_T, Dist_T>(rng, dist)(); } would allow us to rewrite our rand function as follows. unsigned int shorthand_boost_rand() { return generate_rand(boost::uniform_int<>(0, RAND_MAX), boost::mt19937()); } By the way, congratulations on an excellent product to the random.hpp team. -- Christopher Diggins http://www.cdiggins.com

3 3

Intrusive containers: third iteration
by Olaf Krzikalla 24 May '05

24 May '05

Hi, the third version of intrusive containers is available. Beside some bug fixes and minor improvements I have added a real-world example of a triangulation algorithm demonstrating the usefulness of intrusive containers. As usual, you find the file intrusive.zip either in the yahoo file section or here: http://people.freenet.de/turtle++/intrusive.zip Best regards Olaf Krzikalla

2 2

RE: [boost] Re: [1.33.0] Feature freeze reminder
by Martin Bonner 24 May '05

24 May '05

>> Martin Bonner <martin.bonner(a)pitechnology.com> writes: >>> Is it being suggested that "adding backwards compatibility" is a new >>> feature, as opposed to fixing a bug? >>> >>> I think it will be /enormously/ damaging to Boost's reputation for >>> professional quality software if it is not possible to read a 1.32 >>> archive with 1.33. It doesn't take long to build a reputation for >>> "you can never read a file from old versions", and FOREVER to get >>> rid of it. > On May 24, 2005, at 6:45 AM, David Abrahams wrote: >> Yeah, I think this probably falls under "bug fixing," or at least >> "critical feature without which we had better not ship." Douglas Gregor [mailto:doug.gregor@gmail.com] writes: > Yes, it's a bug. I've already given Robert the go-ahead to fix it for > 1.33.0. Thanks Doug. I'd like to take the opportunity to thank you for the job you are doing managing this release. I think you've made the right decision here, and I think you made the right decision on BOOST_FOREACH (even if I would have loved to see that in 1.33). -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

1 0

RE: [boost] Re: Re: [1.33.0] Feature freeze reminder
by Martin Bonner 24 May '05

24 May '05

----Original Message---- From: Jeff Flinn [mailto:TriumphSprint2000@hotmail.com] Sent: 23 May 2005 14:12 To: boost(a)lists.boost.org Subject: [boost] Re: Re: [1.33.0] Feature freeze reminder > "Martin Slater" <mslater(a)hellinc.net> wrote in message > news:428EBB2F.5060101@hellinc.net... >>> The problem is that I want to add code that will handle the >>> previous pointer version. My concern is that users might want to >>> use 1.33 to read archives created under 1.32 and without this >>> addition this won't be possible. I presume that some numbers of >>> people would be effected by such a situation. If not I could just >>> forget it. >> >> Without backwards compatibility with the old shared pointer >> serialization I for one would not be able to upgrade to the latest >> version until it appears. All a pain really as I was looking forward >> to the new improved version. > > I'll second that. > > Jeff Flinn Is it being suggested that "adding backwards compatibility" is a new feature, as opposed to fixing a bug? I think it will be /enormously/ damaging to Boost's reputation for professional quality software if it is not possible to read a 1.32 archive with 1.33. It doesn't take long to build a reputation for "you can never read a file from old versions", and FOREVER to get rid of it. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

3 2

possible bug?
by Nico Blanke 24 May '05

24 May '05

Hi there! Since I read much documentation, and talked to many people on IRC regarding my Problem, I now post it here, because no one can help me. Here is the Source of my C++ App : #include <boost/python.hpp> #include <iostream> using namespace boost::python; void test() { std::cout << "Hello World!" << std::endl; } BOOST_PYTHON_MODULE(test) { def("test", &test); } int main() { Py_Initialize(); std::cout << "INITIALIZED" << std::endl; init_module_test(); std::cout << "MODULE LOADED" << std::endl; FILE * fp; fp = fopen ("test.py","r"); std::cout << "created fp" << std::endl; PyRun_AnyFile(fp, "test.py"); Py_Finalize(); std::cout << "Called PyRun" << std::endl; fclose(fp); } Running this code results in 'Aborted' on init_module_test() ; here's the GDB Output : GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /home/spellbreaker/c++/test [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 13445)] Program received signal SIGABRT, Aborted. [Switching to Thread 16384 (LWP 13445)] 0xb7cc02b1 in kill () from /lib/libc.so.6 (gdb) bt #0 0xb7cc02b1 in kill () from /lib/libc.so.6 #1 0xb7c4d8b8 in pthread_kill () from /lib/libpthread.so.0 #2 0x00003485 in ?? () #3 0x00000006 in ?? () #4 0xb7c52ff4 in ?? () from /lib/libpthread.so.0 #5 0x00000006 in ?? () #6 0xbfffec40 in ?? () #7 0xb7c4dc21 in raise () from /lib/libpthread.so.0 #8 0x00004000 in ?? () #9 0x00000006 in ?? () #10 0xb7da6ff4 in ?? () from /lib/libc.so.6 #11 0xb7cc0052 in raise () from /lib/libc.so.6 #12 0x00000006 in ?? () #13 0xb7da710c in __fpu_control () from /lib/libc.so.6 #14 0xb7da6ff4 in ?? () from /lib/libc.so.6 #15 0x00000000 in ?? () #16 0xb7cc158a in abort () from /lib/libc.so.6 #17 0x00000020 in ?? () #18 0x00000000 in ?? () #19 0x00000000 in ?? () #20 0x00000000 in ?? () #21 0x00000000 in ?? () #22 0x00000000 in ?? () #23 0x00000000 in ?? () #24 0x00000000 in ?? () #25 0x00000000 in ?? () #26 0x00000000 in ?? () #27 0x00000000 in ?? () #28 0x00000000 in ?? () #29 0x00000000 in ?? () #30 0x00000000 in ?? () #31 0x00000000 in ?? () #32 0x00000000 in ?? () #33 0x00000000 in ?? () #34 0x00000000 in ?? () #35 0x00000000 in ?? () #36 0x00000000 in ?? () #37 0x00000000 in ?? () #38 0x00000000 in ?? () #39 0x00000000 in ?? () #40 0x00000000 in ?? () #41 0x00000000 in ?? () #42 0x00000000 in ?? () #43 0x00000000 in ?? () #44 0x00000000 in ?? () #45 0x00000000 in ?? () #46 0x00000000 in ?? () #47 0x00000000 in ?? () #48 0x00000000 in ?? () #49 0x00000000 in ?? () #50 0x00000000 in ?? () #51 0x00000000 in ?? () #52 0x00000000 in ?? () #53 0x00000000 in ?? () #54 0x00000000 in ?? () #55 0x00000000 in ?? () #56 0x09844246 in ?? () #57 0xbfffece0 in ?? () #58 0xb7fce568 in ?? () #59 0x0804a10c in ?? () #60 0x08048f88 in init_module_test () #61 0xb7e780f4 in std::terminate () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5 #62 0xb7e78296 in __cxa_throw () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5 #63 0xb7fbdb67 in boost::python::throw_error_already_set () from /usr/lib/libboost_python.so.1.32.0 #64 0xb7fb496b in boost::python::objects::function::add_to_namespace () from /usr/lib/libboost_python.so.1.32.0 #65 0xb7fb4a93 in boost::python::objects::function::add_to_namespace () from /usr/lib/libboost_python.so.1.32.0 #66 0xb7fb4c04 in boost::python::objects::add_to_namespace () from /usr/lib/libboost_python.so.1.32.0 #67 0xb7fbe170 in boost::python::detail::scope_setattr_doc () from /usr/lib/libboost_python.so.1.32.0 #68 0x08049165 in boost::python::def<void (*)()> () #69 0x08048f86 in init_module_test () #70 0x08048fa2 in main () I hope someone can help me to solve this problem, since I don't see what I did wrong. Best regards, Nico Blanke

2 1

[shared_ptr] problems with ICC/IA64
by Joaquín Mª López Muñoz 24 May '05

24 May '05

When in GCC compatibility mode, ICC on IA64 does not support asm statements, as shown for instance in http://tinyurl.com/7m3bd. I've googled for this, and the references found seem to confirm this fact. This is currently causing countless test failures in FFT-icc_8.1.30/intel-linux. The proposed patch to boost/detail/sp_counted_base.hpp, though not tested (don't have access to the environment), seems to me will solve the problem: basically, it disables the forwarding to the optimized boost/detail/sp_counted_base_gcc_ia64.hpp on the circumstances described. OK to commit? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo 38c38 < #elif defined( __GNUC__ ) && defined( __ia64__ ) --- > #elif defined( __GNUC__ ) && defined( __ia64__ ) && !defined( __INTEL_COMPILER )

2 2

[serialization] Static data members.
by Rene Rivera 24 May '05

24 May '05

Many of the problems that CodeWarrior, and True64, have with the serialization library stem from the behavior of CW to not call constructors for static data members in one particular class in the library. I've come to think that this is standard conforming behavior. The serialization library relies on a static member of a template class being constructed at global initialization time to figure out what all the serialized classes are. The problem is that the template class is being instantiated implicitly. Which for most compilers also instantiates any static members of that template class. It's my understanding that this violates 14.7.1.7: "The implicit instantiation of a class template does not cause any static data members of that class to be implicitly instantiated." Question I have.. Is my understanding correct? Or is this a bug in CW part? For reference the code in question is in "boost/serialization/void_cast.hpp".. http://cvs.sourceforge.net/viewcvs.py/boost/boost/boost/serialization/void_… http://tinyurl.com/9s5jb The template class is void_caster_primitive, and it's instantiated from the void_cast_register function at the bottom. -- -- 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

3 12

[Threads] Failures on msvc, msvc-stlport
by Doug Gregor 24 May '05

24 May '05

The Threads library is failing the majority of the regression tests on Visual C++ 6.0, where it was previously supported. Are we continuing to support this compiler in the Thread library? If so, we need to fix these bugs immediately; if not, we need to mark the toolsets unusable with the Thread library. Doug

5 6

RE: [boost] Re: Building from current CVS
by Marcin Tustin 24 May '05

24 May '05

I've managed to use the vc71 .sln files to build the serialization library, but now I have a question that probably seems pretty stupid: How does Visual Studio know which .lib file to try to link against? I'm using the headers from CVS, and Visual studio in compiling my project is trying to link against libboost_serialization-vc71-mt-sgd-1_33.lib, but my project does not mention this file, so I am confused about how to point Visual studio at the library generated from the CVS source. > -----Original Message----- > From: Keith MacDonald [mailto:boost@mailclan.net] > Sent: 22 May 2005 11:05 > To: boost(a)lists.boost.org > Subject: [boost] Re: Building from current CVS > > Here's a batch file that I use to build Boost from CVS with > VC 7.1 on XP: > > ========= build7.bat ========= > REM Build Boost libraries with VC7.1 > SET PYTHON_ROOT=C:\Apps\Python24 > SET PYTHON_VERSION=2.4 > REM First build JAM > CD tools\build\jam_src > CALL build.bat > REM Now use JAM to build BOOST > CD ..\..\.. > @echo "Building Boost with VC 7.1 ..." > tools\build\jam_src\bin.ntx86\bjam > "-sTOOLS=vc-7_1" -sICU_PATH=F:\Dev\icu-3.2 > build7.log @ECHO > "Finished. See build7.log" > ========================== > > I've not figured out how to use bjam with v2 rules, so a > similar batch file for VC 8.0 works but you get a lot of > warnings about unknown and obsolete compiler options. > > Keith MacDonald > > "Marcin Tustin" <mt(a)it-innovation.soton.ac.uk> wrote in > message > news:1F5A05DA40944243A29DC3C135A2E72F19CF6F@mailserver-2.it-in novation.soton.ac.uk... > > > > I'm trying to build from the current CVS (actually about a > week old), > > and it has some weird problem with creating files and directories. > > > > > > When trying to build with a version of Jam from 1.32, it > always falls > > over trying to create a file or directory, normally > mentioning Mkdir1 > > first. > > > > When trying to build the version of Jam that comes with the CVs > > source, it is able to build jam0.exe, but when it comes > time to make > > bin.ntx86 it fails; and if that directory exists, the jam > executable > > is not created; instead an error about "spawn: No such file or > > directory" is emittted. > > > > I am using vc 7.1. > > > > Any ideas for a better way to build the boost libraries? > > > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > > >

3 2

[type traits] is_abstract expected failures
by Doug Gregor 24 May '05

24 May '05

The following compilers are failing is_abstract_test: - cw-9_5-darwin - gcc-3_3-darwin - cw-9_4 From the list of compilers that are already expected to fail this test (include CW 9.3 and GCC 3.3.x), I think they should be marked as known failures and will do so unless anyone objects. Doug

2 1

Boost HEAD: does not compile with Borland C++ 5.6.5 (patch included)
by "André Heynatz" 24 May '05

24 May '05

Hello, there is a version check in boost/config/compilers/borland.hpp for the misfeature BOOST_NO_SFINAE, Borland C++ 5.6.5 still lacks proper support for this, the patch appended speaks for itself. Greetings, André Heynatz -- 5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail +++ GMX - die erste Adresse für Mail, Message, More +++

4 3

[Boost-bugs] [ boost-Bugs-1206673 ] Boost.Optional documentation typo.
by SourceForge.net 23 May '05

23 May '05

Bugs item #1206673, was opened at 2005-05-22 22:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1206673&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sebastian Redl (cornedbee) Assigned to: Nobody/Anonymous (nobody) Summary: Boost.Optional documentation typo. Initial Comment: Not sure if documentation gets fixed in the CVS. Optional has no documentation in the nightly doc builds, so here we go. The Optional documentation contains this about operator >: ------------- bool operator > ( optional<T> const& x, optional<T> const& y ); Returns: !( y < x ); ------------- This is a typo in the documentation. The implementation correctly implements operator (x > y) as (y < x), without the negation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1206673&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=7412&alloc_id=16344&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 1

[1.33.0] Feature freeze reminder
by Doug Gregor 23 May '05

23 May '05

We are in feature freeze. No new features can be added to any library without specific approval from me. We still have many, many bugs to fix before this release. We CAN NOT afford to create any more bugs. Please analyze and fix the bugs you have. Doug Gregor 1.33.0 Release Manager

8 9

[Boost-bugs] [ boost-Support Requests-1207057 ] Boost regex for Novell Netware
by SourceForge.net 23 May '05

23 May '05

Support Requests item #1207057, was opened at 2005-05-23 13:10 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=1207057&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tribhuwan (yadtr01) Assigned to: Nobody/Anonymous (nobody) Summary: Boost regex for Novell Netware Initial Comment: Does somebody have a binary version of boost Regex for Novell Netware? If not, I need to use Regex library in my application so I need to port it onto NetWare, Compiler used is CodeWarrior, any help in this regard especially in configuring/generating configuration files would be highly appreciated. Thanks & Regards, Tribhuwan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1207057&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=7412&alloc_id=16344&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

RE: [boost] Re: Building from current CVS
by Marcin Tustin 23 May '05

23 May '05

Thanks. But does anyone else find that bjam is unable to create files/directories? I would think that it is a problem with filesystem permissions were it not that I can use mkdir and that jam0.exe does get built, as do the obj files. > -----Original Message----- > From: Keith MacDonald [mailto:boost@mailclan.net] > Sent: 22 May 2005 11:05 > To: boost(a)lists.boost.org > Subject: [boost] Re: Building from current CVS > > Here's a batch file that I use to build Boost from CVS with > VC 7.1 on XP: > > ========= build7.bat ========= > REM Build Boost libraries with VC7.1 > SET PYTHON_ROOT=C:\Apps\Python24 > SET PYTHON_VERSION=2.4 > REM First build JAM > CD tools\build\jam_src > CALL build.bat > REM Now use JAM to build BOOST > CD ..\..\.. > @echo "Building Boost with VC 7.1 ..." > tools\build\jam_src\bin.ntx86\bjam > "-sTOOLS=vc-7_1" -sICU_PATH=F:\Dev\icu-3.2 > build7.log @ECHO > "Finished. See build7.log" > ========================== > > I've not figured out how to use bjam with v2 rules, so a > similar batch file for VC 8.0 works but you get a lot of > warnings about unknown and obsolete compiler options. > > Keith MacDonald > > "Marcin Tustin" <mt(a)it-innovation.soton.ac.uk> wrote in > message > news:1F5A05DA40944243A29DC3C135A2E72F19CF6F@mailserver-2.it-in novation.soton.ac.uk... > > > > I'm trying to build from the current CVS (actually about a > week old), > > and it has some weird problem with creating files and directories. > > > > > > When trying to build with a version of Jam from 1.32, it > always falls > > over trying to create a file or directory, normally > mentioning Mkdir1 > > first. > > > > When trying to build the version of Jam that comes with the CVs > > source, it is able to build jam0.exe, but when it comes > time to make > > bin.ntx86 it fails; and if that directory exists, the jam > executable > > is not created; instead an error about "spawn: No such file or > > directory" is emittted. > > > > I am using vc 7.1. > > > > Any ideas for a better way to build the boost libraries? > > > > > > _______________________________________________ > > Unsubscribe & other changes: > > http://lists.boost.org/mailman/listinfo.cgi/boost > > > > > > >

1 0