- Boost - lists.boost.org

Important: RC_1_33_0 -> HEAD merge
by Doug Gregor 12 Dec '05

12 Dec '05

Now that 1.33.1 is out and the RC_1_33_0 branch is most likely closed for good, I've merged many of the changes from the RC_1_33_0 branch back to HEAD so that we don't lose all of the minor tweaks we made at the end. For many changes, the merge was so trivial that I've just committed the results. However, some libraries seemed to get quite out-of-sync. This happens when changes were made on both HEAD and RC_1_33_0, and CVS can't figure out how to merge those changes. These libraries are: Date-Time Iostreams Parameter Pointer containers Range Regex Serialization uBLAS The authors of these libraries should look at the merged results to determine what changes need to be made in HEAD. Otherwise, fixes that we have done for 1.33.1 will be forgotten and lost. To do so, have a clean checkout of CVS HEAD available and run something like this: cvs -z6 update -j Version_1_33_0 -j Version_1_33_1 boost/iostreams libs/iostreams (You may want to redirect the output of that command to a file; there's a lot of information in there) Look for "conflicts" in the output to see went wrong, then dig through conflicting files looking for sections between <<<<< and ==== (HEAD code) and ===== and >>>>> (RC_1_33_0 code). Once you've cleaned up everything, commit back to head and you'll be done. Doug

8 7

[BGL] auto index property maps in the boost vault
by Aaron Windsor 12 Dec '05

12 Dec '05

Hi all, I've put some files in the boost vault under algorithms/graph in a package I'm calling "auto index property maps." I developed these in response to a thread on boost-users a few months back (http://tinyurl.com/bezjr) and a steady stream of questions on this mailing list and boost-users about how to use/create vertex and edge index maps when they aren't provided for you. Vertex index maps are property maps that map the vertices of a graph bijectively into the range [0..num_vertices(g)). Edge index maps map edges bijectively into [0..num_edges(g)). Many BGL algorithms require a vertex or edge index map, and one can be supplied either in the form of an interior property or an external property map. Auto index property maps are external property maps that were created with ease of use in mind. In short, whenever a vertex index map is expected for the graph g, you can substitute the expression "make_auto_vertex_index(g)" and everything will work as expected. Similarly, if an edge index property map is expected, you can use the expression "make_auto_edge_index(g)" instead. It's my hope that the auto index property maps will provide a quick solution to those looking to get started with the BGL who aren't yet worried about delving into the details of working with internal properties, which seems to be a difficult issue for a lot of beginners. Auto index property maps can be used while prototyping and replaced later with interior properties if efficiency is an issue. Any feedback would be most appreciated. I've tested everything with gcc 3.4.4 on cygwin. Aaron

3 5

[Wave] Wrong phase for trigraphs? Generator interface?
by Daryle Walker 12 Dec '05

12 Dec '05

[Sorry if this has already been reported, fixed, and/or superceded.] Looking at <http://www.boost.org/libs/wave/doc/token_ids.html>, I see various kinds of tokens. There are tokens for the preprocessor that are seen by the lexer and don't make it to the preprocessing iterator level. The other sets of tokens do make it to that level, modulo any transformations. The trigraphs are put in the operator token list. However, trigraphs should not be there. They are processed before anything else, even before the preprocessor tokens. So there should be another level of lexer working here. As is, it doesn't seem that you could use the trigraph for "#", "??=", for preprocessor directives. ??=include <cstdio> // this should work On a related note, I thought maybe Wave should use a generator interface: template < typename Iterator, typename FileID > class phase1 { public: phase1( Iterator b, Iterator e, FileID id ); operator bool() const; // TRUE while not done cpp_p1_char_type operator ()(); }; template < typename Iterator, typename FileID > class phase2 { public: explicit phase2( phase1<Iterator, FileID> const &p ); operator bool() const; // TRUE while not done cpp_p2_line_string_type operator ()(); }; //... You generally can't rewind, of course. The cpp_p1_char_type would contain the expanded character's identity AND some indicator of its location (starting iterator, file ID, and line, row, and un-lined offset numbers). The cpp_p2_line_string_type would carry the locations for each character in its string. Then the tokens of later phases would know the location of their first characters. -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com

3 2

BOOST_HAS_NRVO not being set for VC++ 8.0
by Beman Dawes 12 Dec '05

12 Dec '05

According to http://msdn.microsoft.com/visualc/default.aspx?pull=/library/en-us/dnvs05/h…, VC++ 8.0 now support NRVO. Config info isn't reporting BOOST_HAS_NRVO as being set. Should this be changed? --Beman

5 6

boost::function / boost::signal convenience
by David Gruener 12 Dec '05

12 Dec '05

Hi, I'd like to write the "Preferred syntax" of a signal while including a header for a fixed number of parameters. This works for boost::function, but not for boost::signal. Surprisingly, it seems that signal1.hpp does only generate a signal1 template, in contrast to function1.hpp. :[ Couldn't that be aligned to boost::function? #include <boost/function/function1.hpp> typedef boost::function1<void, void> F1; // compiles typedef boost::function<void (void)> F2; // compiles #include <boost/signals/signal1.hpp> typedef boost::signal1<void, void> S1; // compiles typedef boost::signal<void (void)> S2; // does not compile -- David

1 0

Re: [boost] asio formal review begins
by Oliver.Kowalke＠infineon.com 12 Dec '05

12 Dec '05

Hello, what about multicast and raw sockets (ICMP, IGMP, ...)? SIGPIPE is blocked by the ctor of basic_demuxer - I think it would be better to block SIGPIPE only in the functions reading from the socket and after that reset to the original signal handler. EINTR is not handled in the reading/writing functions? Is it correct, that asio doesn't use AIO System Interfaces from the OS (like aiocb, aio_read, aio_write, aio_suspend, ...)? So long, Oliver

3 2

[Boost-bugs] [ boost-Bugs-1378631 ] Problems with native_file_string() on windows
by SourceForge.net 12 Dec '05

12 Dec '05

Bugs item #1378631, was opened at 2005-12-12 02:25 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=1378631&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: filesystem Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Beman Dawes (beman_dawes) Summary: Problems with native_file_string() on windows Initial Comment: It seems I have stumbled upon a known bug with path::native_file_string() on windows. The returned std::string object can not be destroyed when going out of scope. A similar error occurs when using directory_iterator::leaf(). Has anyone developed a patch for this yet? Thanks, barry bazbishop(a)btinternet.com see also: http://aspn.activestate.com/ASPN/Mail/Message/boost/1968006 http://archives.free.net.ph/message/20051111.035907.1ed81e73.en.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1378631&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

using filesystem path with program_options
by Chris Weed 12 Dec '05

12 Dec '05

Hi, I would like to have the program_options functions parse a boost::filesystem path. For example something like the following code. However, this doesn't seem to work. The error seems to suggest the problem is a lack of operator >> for path. Is it possible to make this work? namespace po = boost::program_options; namespace fs = boost::filesystem; po::options_description generic("Allowed options"); generic.add_options() ("help", "produce help message") ("output-path,o",po::value<fs::path>(), "output path") ("input-file", po::value<fs::path>(), "input file") ; po::positional_options_description p; p.add("input-file", -1); po::variables_map vm; po::store(po::command_line_parser(argc, argv). options(generic).positional(p).run(), vm); po::notify(vm); fs::path input_path; if(vm.count("input-file")) { input_path = vm["input-file"].as<fs::path>(); } Error: boost_1_33_0/boost/lexical_cast.hpp: In member function 'bool boost::detail::lexical_stream<Target, Source>::operator>>(InputStreamable&) [with InputStreamable = boost::filesystem::path, Target = boost::filesystem::path, Source = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': boost_1_33_0/boost/lexical_cast.hpp:221: instantiated from 'Target boost::lexical_cast(const Source&) [with Target = boost::filesystem::path, Source = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]' ../radarvision/MIDAS/build/boost_1_33_0/boost/program_options/detail/value_semantic.hpp:83: instantiated from 'void boost::program_options::validate(boost::any&, const std::vector<std::basic_string<charT, std::char_traits<charT>, std::allocator<_T2> >, std::allocator<std::basic_string<charT, std::char_traits<charT>, std::allocator<_T2> > > >&, T*, long int) [with T = boost::filesystem::path, charT = char]' boost_1_33_0/boost/program_options/detail/value_semantic.hpp:151: instantiated from 'void boost::program_options::typed_value<T, charT>::xparse(boost::any&, const std::vector<std::basic_string<charT, std::char_traits<charT>, std::allocator<_T2> >, std::allocator<std::basic_string<charT, std::char_traits<charT>, std::allocator<_T2> > > >&) const [with T = boost::filesystem::path, charT = char]' main.cpp:32: instantiated from here boost_1_33_0/boost/lexical_cast.hpp:165: error: no match for 'operator>>' in '((boost::detail::lexical_stream<boost::filesystem::path, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >*)this)->boost::detail::lexical_stream<boost::filesystem::path, std::basic_string<char, std::char_traits<char>, std::allocator<char> > >::stream >> output' /atech/gcc-4.0.0/lib/gcc/sparc-sun-solaris2.8/4.0.0/../../../../include/c++/4.0.0/istream:131: note: candidates are: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_istream<_CharT, _Traits>& (*)(std::basic_istream<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] /atech/gcc-4.0.0/lib/gcc/sparc-sun-solaris2.8/4.0.0/../../../../include/c++/4.0.0/istream:134: note: std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT, _Traits>::operator>>(std::basic_ios<_CharT, _Traits>& (*)(std::basic_ios<_CharT, _Traits>&)) [with _CharT = char, _Traits = std::char_traits<char>] Thanks, Chris

3 4

[Boost-bugs] [ boost-Bugs-1378542 ] problem with boost::algorithm::split
by SourceForge.net 12 Dec '05

12 Dec '05

Bugs item #1378542, was opened at 2005-12-12 06:39 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=1378542&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: liner (liner) Assigned to: Nobody/Anonymous (nobody) Summary: problem with boost::algorithm::split Initial Comment: string str("*word1-word2*word3-"); vector<std::string> ResultCopy; split(ResultCopy, str, is_any_of("-*"), token_compress_on); for(unsigned int nIndex=0; nIndex<ResultCopy.size(); nIndex++) { cout << nIndex << ":" << ResultCopy[nIndex] << endl; }; The output is: 0: 1:word1 2:word2 3:word3 4: Is this a bug? In my opinion the output should be: 0:word1 1:word2 2:word3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=1378542&group_… ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

asio formal review
by Matthew Nourse 12 Dec '05

12 Dec '05

I vote to accept asio into boost. Potential bias disclosure: I'm friends with Chris Kohlhoff. I have been writing asynchronous servers and clients with asio and boost for about 20 months. The following asio & boost -based server applications are currently running in commercial production systems: * a gateway from a proprietary networking API to HTTP. Up since November 2004. Windows+VC7. * a custom authenticating HTTP proxy. Up since February 2005. Linux+gcc. * an HTTP gateway to a proprietary IM system. Up since May 2005 except short upgrades to my code. Linux+gcc. * an XMPP (Jabber) gateway for the same proprietary IM system. Up since August 2005 except short upgrades to my code. Linux+gcc. * a lightweight publish-subscribe mechanism. Up since August 2005. Linux+gcc. I've found asio's implementation to be extremely efficient. For example the publish-subscribe mechanism can handle 500 requests/second without any detectable CPU usage on a 3Ghz P4 even though my code is untuned & does more memory allocations than is strictly necessary. I found the asio design philosophy and documentation relatively easy to understand however I before I used asio I had already written aynsc socket applications using Windows' IO completion ports. I am not a template-based design expert nor am I a longstanding boost user. My first use of boost was when I started my first asio application in August 2004. Matt

1 0