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

[Boost-bugs] [ boost-Support Requests-1114084 ] program_options bug?
by SourceForge.net 01 Feb '05

01 Feb '05

Support Requests item #1114084, was opened at 2005-02-01 08:03 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=1114084&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: program_options bug? Initial Comment: I use Borland C++ 6 under Windows and I am trying to use program_options library. It seems that if I add a nonhandled parameter to command line the program hangs. For example using first.cpp and adding --unhandled to command line. in parsers.hpp: template<class charT> basic_parsed_options<charT> basic_command_line_parser<charT>::run() const { // Presense of parsed_options -> wparsed_options conversion // does the trick. ==== HERE! ===> return basic_parsed_options<charT>( common_command_line_parser::run()); } thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=207586&aid=1114084&group_… ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

2 2

Problem with Intel 8.1 Linux regression tests
by Joaquín Mª López Muñoz 01 Feb '05

01 Feb '05

Seems like some stdlib headers are missing: http://tinyurl.com/4pkjh The same error happens accross multiple tests of different libraries. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 2

[iostreams] [regression] iostreams added to CVS
by Jonathan Turkanis 01 Feb '05

01 Feb '05

Dear all, The iostreams library has been added to CVS. I've also added a line to boost-root/status/Jamfile. Is this enough to have the library included in the regression tests, or is something more required? Jonathan

4 8

lexical_cast: Needing to work for MSVC 6 (and similar)?
by Terje Slettebø 01 Feb '05

01 Feb '05

Hi. When testing it, I've found that the CVS version of lexical_cast apparently doesn't work for MSVC 6 (at least with my setup). I get the following errors when running the unit test: boost/lexical_cast.hpp(178) : error C2059: syntax error : '<' boost/lexical_cast.hpp(180) : see reference to class template instantiation 'boost::detail::lexical_stream<Target,Source>' being compiled boost/lexical_cast.hpp(178) : error C2238: unexpected token(s) preceding ';' boost/lexical_cast.hpp(180) : see reference to class template instantiation 'boost::detail::lexical_stream<Target,Source>' being compiled boost/test/utils/basic_cstring/bcs_char_traits.hpp(120) : error C2143: syntax error : missing ',' before '<' boost/test/utils/basic_cstring/bcs_char_traits.hpp(120) : error C2059: syntax error : '<' boost/test/utils/basic_cstring/bcs_char_traits.hpp(120) : fatal error C1903: unable to recover from previous error(s); stopping compilation I also see that the current regression test doesn't include MSVC 6 (http://www.meta-comm.com/engineering/boost-regression/developer/conversion. html). Because of this, Kevlin Henney and I was wondering whether or not MSVC 6 support for this component (and components in Boost in general) is no longer demanded, or in general, what the required conformance level is? If MSVC 6 support is still needed, I guess the above problems should be fixed. It seems to crash out in Boost.Test, as well. I see there are a few other failures in the regression test for more conformant compilers, though, and I'll look into these. Regards, Terje

3 2

Re: shared_ptr inheritance query
by Dave Handley 01 Feb '05

01 Feb '05

Peter Dimov wrote: > Can you separate the interface and implementation parts of the policy into > two classes, then inherit publicly from policy_interface and privately > from > policy_implementation? Unfortunately not, the policy has to be able to generate shared pointers from itself - hence it needs access to shared_from_this. If I used a multiple inheritance solution, I would be forced to dynamic_cast across to the enable_shared_from_this class, which I don't want to do. Dave Handley

2 1

g++ 4.0 and typeof/operator overloading based metaprogramming
by Daniel James 01 Feb '05

01 Feb '05

Hello everyone, I've been trying out a pre-release of g++ 4.0, and its typeof now works a lot better than the older versions. This allows it to be used for metaprogramming. As an example, I've attached a compile time factorial implemented mainly using operator overloads (it's not commented at all, but should be pretty easy to understand for most people on this list). I think it would be possible to write a metaprogramming library which would have much nicer syntax (borrowing techniques from lamba & phoenix), and integrate well with mpl. I suppose that since such a library would only work on gcc for now (or do any other compilers have a good enough typeof?), it might not be appropriate for boost, but I thought this might be of interest here anyway. Daniel

2 2

Wave C++ preprocessor - Boost Review
by Tom Brinkman 01 Feb '05

01 Feb '05

I would like to start the boost wave review in the next couple of days. If you would like to volunteer to be the review manager for this very intersting library, please contact me. Tom Brinkman at reportbase(a)yahoo.com Boost Review Wizard A short description of the library follows: The Wave C++ preprocessor library is a Standards conformant implementation of the mandated C99/C++ preprocessor functionality packed behind a simple to use interface, which integrates well with the well known idioms of the Standard Template Library (STL). It is not a monolitic application, it's rather a modular library, which exposes mainly a context object and an iterator interface. The context object helps to configure the actual preprocessing process (as search path's, predefined macros, etc.). The exposed iterators are generated by this context object too. Iterating over the sequence defined by the two iterators will return the preprocessed tokens, which are to be built on the fly from the given input stream. The C++ preprocessor iterator itself is fed by a C++ lexer iterator, which implements an abstract interface. The C++ lexers packaged with the Wave library may be used standalone, too, and are not tied to the C++ preprocessor iterator at all. The flexible interface exposed by the library makes it usable in a variety of applications ranging from simple lexing (tokenising) a C99/C++ input stream to complex preprocessing with fine control over the details of the macro expansion process. For instance it's very simple to inject your own #pragma handling into the preprocessing, allowing to expand it in virtually unlimited ways. The Wave C++ preprocessor library is known to be compilable on VC7.1, Intel7.1 and 8.0, gcc 3.2.x and 3.3.x. Work is currently underway to make it usable with VC6.5 as well. The library contains samples, which show different ways of it's usage. A full blown preprocessing command line oriented driver application is included in the Boost tools section as well. The review candidate version of Wave is accessible here: http://spirit.sourceforge.net/dl_more/wave-1.1.12.zip additionally it is included in the Boost-sandbox CVS. If you're interested in what's new or changed since the last releases, please refer to the enclosed documentation or the changelog file contained inside the archive. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

protection from unintended ADL
by Gennadiy Rozental 01 Feb '05

01 Feb '05

I noticed that in some places we are using extra namespace for protection from unintended ADL. Is there any rationale for: 1. Why we need that? 2. Why namely this solution is prefered? 3. In which case we need to do so? Gennadiy

2 1

iostreams stdio_filter motivating example
by christopher diggins 01 Feb '05

01 Feb '05

I may finally have a good motivating example for stdio_filter: Consider the roman_numerals.cpp example from the Boost spirit library at http://tinyurl.com/3qw4k If I make a couple of minor modifications exclusively to the main, such as remove the superflous user prompting and rename it to something legal, i.e.: int RomanNumeralParse() { string str; while (getline(cin, str)) { if (str[0] == 'q' || str[0] == 'Q') break; unsigned n = 0; roman roman_p(n); if (parse(str.c_str(), roman_p).full) { cout << n << endl; } else { cerr << "parsing failure" << endl; return 1; } } return 0; } Using my current version of my filters library (not available online yet) I can now reuse the entire program from another, such as the following: void RomanNumeralParserTest() { stringstream sIn("MCMLXXIV"), sOut; sIn > SimpleMainFilter(RomanNumeralParse) > sOut; int n; sOut >> n; TEST(n == 1974); } Many examples from the Spirit examples, can be refactored in this manner, to become reusable with relatively little effort. I suppose one of the calculators would be even more interesting. Is this a good motivating example for introducing a stdio_filter into boost::iostreams? Christopher Diggins Object Oriented Template Library (OOTL) http://www.ootl.org

3 2