- Boost - lists.preview.boost.org

Re: [boost] Re: static sized strings
by Reece Dunn 22 Jun '04

22 Jun '04

Rob Stewart wrote: >From: "Reece Dunn" > > John Nagle wrote: > > >Reece Dunn wrote: > > >>John Nagle wrote: > > >>The problems arise in the interation with basic_string_impl and how to > > >>implement swap and functions that require constructing a string >object. > > >Why do you need to construct a string object to swap? > > >Just swap one character at a time. > > > > [2] How do I implement the swap function? The solution I arrived at is >the > > one you suggest: to swap the data character-by-character. What you have >to > >Unfortunately, that makes swap() O(N), but it does allow it to be >nothrow. Unfortunately. To swap the impl members would make it O(1), but would lead to unpredictable behaviour since the two strings swap pointers to their fixed_string buffers. The approach I use is the best I could find. > > consider when doing this is that the strings don't exceed capacity, > > resulting in additional logic. > >That should fail, shouldn't it? Yes, that would mean a swap() >that throws, but the strings aren't really swapped if you only >swap some characters. The same is true though of all the other functions (e.g. assign): what happens if the string doesn't fit? >I'm not sure which is worse: a swap() that throws or only >partially swapping. The former violates exception safety >guarantee assumptions made by other code, but the latter means >that swap() may not really swap, which violates semantics. I have gone for a clip to capacity design for all the fixed_string functions. Thus: fixed_string< 5 > str; str.assign( "Hello there!" ); // str == "Hello" Any error handling policy that is implemented has it's own advantages and disadvantages. Another problem with using exceptions is adapting C code: there may not be any try-catch blocks in the code, resulting in unhandled exceptions. The clip strategy is not ideal either, but I believe it is the best approach considering the code it is abstracting: you will usually have a buffer large enough for the application you are using it for (filenames/paths, command line strings, URLs, etc.) One possibility is making the error handling a policy class so it can be adapted to suit the users needs with the current behaviour as default. Regards, Reece _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger

2 1

RE: [boost] [test] [minmax] failure on gcc 2.95
by Rozental, Gennadiy 21 Jun '04

21 Jun '04

> As shown in http://tinyurl.com/3xdyq, > Boost.Test fails to build on gcc 2.95 with stlport. The error > message is: > > /boost/head-regression/boost/boost/minmax.hpp: In function > `const size_t & boost::std_min<size_t>(const size_t &, const > size_t &)': > > /boost/head-regression/boost/libs/test/build/../src/test_tools > .cpp:375: instantiated from here > /boost/head-regression/boost/boost/minmax.hpp:26: `min' > undeclared (first use this function) > > Is it possible that authors of either Boost.Test or > boost/minmax.hpp take care of this error? I'd prefer it to be addressed on minmax.hpp level. After all it's the header responsible for min and max. Gennadiy.

3 3

Typo in boost/graph/properties.hpp
by Janusz Piwowarski 20 Jun '04

20 Jun '04

Hello, I'm attaching patch, as in subject. Also, there isn't undefined variable x in boost/graph/graph_test.hpp (test_readable_vertex_property_graph and test_vertex_property_graph templates). I have no idea what it is. Regards, Janusz

2 1

threads
by val salamakha 20 Jun '04

20 Jun '04

Dear William E. Kempf, I installed the latest version of the boost-1.31.0 on Win xp pro with vc7.1 and tried to use the thread library. During the first build of several samples, MSVS(vc71) gave me a warning about the errors. However I ignored the errors and select option to proceed(the same result is in other case). It seems to me the samples work correctly in spite of errors and warning located below my message. I had no warning or errors on the next build of the same sample at all. Would you please tell me what is going on? And how do I fix it? Thanks Valery Salamakha VC71_ROOT\include\stdexcept(14): see declaration of 'std::logic_error' c:\Boost\include\boost-1_31\boost\thread\exceptions.hpp(28) : see declaration of 'boost::lock_error' c:\Boost\include\boost-1_31\boost\thread\thread.hpp(78): warning C4251: 'boost::thread_group::m_threads' : class 'std::list<_Ty>' needs to have dll-interface to be used by clients of class 'boost::thread_group' with [ _Ty=boost::thread * ] c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(36): warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::mutex' c:\Boost\include\boost-1_31\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(35) : see declaration of 'boost::mutex' c:\Boost\include\boost-1_31\boost\thread\thread.hpp(38): warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread' c:\Boost\include\boost-1_31\boost\thread\thread.hpp(67): warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::thread_group' c:\Boost\include\boost-1_31\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(114): warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::timed_mutex' c:\Boost\include\boost-1_31\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(113) : see declaration of 'boost::timed_mutex' c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(74): warning C4275: non dll-interface class 'boost::noncopyable' used as base for dll-interface class 'boost::try_mutex' c:\Boost\include\boost-1_31\boost\noncopyable.hpp(22) : see declaration of 'boost::noncopyable' c:\Boost\include\boost-1_31\boost\thread\mutex.hpp(73) : see declaration of 'boost::try_mutex' c:\Boost\include\boost-1_31\boost\thread\exceptions.hpp(29): warning C4275: non dll-interface class 'std::logic_error' used as base for dll-interface class 'boost::lock_error' c:\Boost\include\boost-1_31\boost\thread\exceptions.hpp(35): warning C4275: non dll-interface class 'std::runtime_error' used as base for dll-interface class 'boost::thread_resource_error' c:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include\stdexcept(136) : see declaration of 'std::runtime_error' c:\Boost\include\boost-1_31\boost\thread\exceptions.hpp(34) : see declaration of 'boost::thread_resource_error' __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail

5 10

RE: [boost] Re: static sized strings (struct hack)
by Reece Dunn 20 Jun '04

20 Jun '04

John Nagle wrote: >Reece Dunn wrote: >>John Nagle wrote: >>> I think we're back to using an abstract base class. >>>The hacks to get around it introduce worse problems. >>I would agree. I have been trying to find a way around the problem and >>have (sortof) by having a base class: >> >> template< typename CharT > >> class string_base >> { >> private: >> size_t len, cap; // length & capacity >> CharT * buf; // data buffer >> public: >> string_base( CharT * b, size_t c, size_t l ): >> len( l ), cap( c ), buf( b ){} >> // non-virtual implementation >> }; >> >> template< size_t n, typename CharT > >> class fixed_string: public string_base >> { >> private: >> CharT data[ n + 1 ]; >> public: >> fixed_string(): string_base( data, n + 1 ){} >> }; >That's a much better approach than the previous one. >It's sound C++, and it's simple. >All the operations go in string_base. fixed_string >need only allocate space. Where do you hit a problem? The problems arise in the interation with basic_string_impl and how to implement swap and functions that require constructing a string object. Both string_base and fixed_string must operate through basic_string_impl to allow basic_string operations. I suppose this should be done in a heirarchy similar to the current one, having swap virtual (you don't want to swap internal pointers!) and using the current system for the object construction functions, but it may be possible to have substr virtual, I'm not sure yet. I shall have a go at this and report back when I have a working implementation. Regards, Reece _________________________________________________________________ Stay in touch with absent friends - get MSN Messenger http://www.msn.co.uk/messenger

2 1

[Boost-bugs] [ boost-Bugs-976241 ] Compiler error for tokenizer on Solaris
by SourceForge.net 20 Jun '04

20 Jun '04

Bugs item #976241, was opened at 2004-06-20 13:51 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=976241&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tom Aratari (stosys) Assigned to: Nobody/Anonymous (nobody) Summary: Compiler error for tokenizer on Solaris Initial Comment: When trying to upgrade to boost 1_31, Forte 8.0 (CC: Sun C++ 5.5 Patch 113817-03 2003/10/14) gives the following error for the code snip: typedef boost::tokenizer<boost::char_separator<char> > tokenizer; boost::char_separator<char> seperator (sDroppedDelimiters, sKeptDelimiters, boost::keep_empty_tokens); tokenizer tokens( sString, seperator ); for (tokenizer::iterator tok_iter = tokens.begin(); tok_iter != tokens.end(); ++tok_iter) vInVector.push_back( *tok_iter ); Copiler error: "/home/dev/cm/THIRD_PARTY/boost/include/boost/iterat or/iterator_facade.hpp", line 623: Error: Could not find a match for boost::iterator_core_access::equal<boost::iterator_core _access::Facade1, boost::iterator_core_access::Facade2>(const boost::token_iterator<boost::char_separator<char, std::char_traits<char>>, const char*, std::string>, const boost::token_iterator<boost::char_separator<char, std::char_traits<char>>, const char*, std::string>, boost::is_convertible<boost::token_iterator<boost::char _separator<char, std::char_traits<char>>, const char*, std::string>, boost::token_iterator<boost::char_separator<char, std::char_traits<char>>, const char*, std::string>>). "MDSStringHelpers.cxx", line 183: Where: While instantiating "boost::operator! =<boost::token_iterator<boost::char_separator<char, std::char_traits<char>>, const char*, std::string>, std::string,boost::forward_traversal_tag, const std::string &, int, boost::token_iterator<boost::char_separator<char, std::char_traits<char>>, const char*, std::string>, std::string, boost::forward_traversal_tag, const std::string &, int>(const boost::iterator_facade<boost::token_iterator<boost::cha r_separator<char, std::char_traits<char>>, const char*, std::string>, std::string, boost::forward_traversal_tag, const std::string &, int>&, const boost::iterator_facade<boost::token_iterator<boost::cha r_separator<char, std::char_traits<char>>, const char*, std::string>, std::string, boost::forward_traversal_tag, const std::string &, int>&)". "MDSStringHelpers.cxx", line 183: Where: Instantiated from non-template code. Has anyone else complianed about this? Thanks Tom ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=107586&aid=976241&group_i… ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/boost-bugs

1 0

Another BoostBook/Doxygen bug?
by Angus Leeming 18 Jun '04

18 Jun '04

Is it possible to get the BoostBook/Doxygen documentation system to include my commentary? This is the header file #include <boost/child/detail/pipe_mode.hpp> namespace boost { namespace child { /// A stateless class providing constants and typenames. struct pipes_base { /// A type used to specify how to communciate with the child process. typedef detail::pipe_mode pipe_mode; /// Write to the child's standard input stream. static const pipe_mode child_stdin = pipe_mode(1); /// Read from the child's standard output stream. static const pipe_mode child_stdout = pipe_mode(2); /// Read from the child's standard error stream. static const pipe_mode child_stderr = pipe_mode(4); /// Redirect the child's stderr to its stdout. static const pipe_mode redirect_child_stderr = pipe_mode(8); /// No pipes are to be used. static const pipe_mode no_pipes = pipe_mode(16); }; } // namespace child } // namespace boost And below is the generated documentation. See how all the descriptions of the constants have dissappeared. Also see how the typedef has been 'modified'. Regards, Angus Struct pipes_base boost::child::pipes_base ? A stateless class providing constants and typenames. Synopsis struct pipes_base { // types typedef unspecified pipe_mode; // A type used to specify how to communciate with the child process. static const pipe_mode child_stdin; static const pipe_mode child_stdout; static const pipe_mode child_stderr; static const pipe_mode redirect_child_stderr; static const pipe_mode no_pipes; };

2 3

[Test] Link problems
by David B. Held 18 Jun '04

18 Jun '04

unit_test_log.o: In function `boost::unit_test::unit_test_log::unit_test_log[not-in-charge]()': /usr/include/c++/3.3.2/bits/stl_heap.h:221: undefined reference to `boost::unit_test::ut_detail::msvc65_like_log_formatter::msvc65_like_log_for matter[in-charge] (boost::unit_test::unit_test_log const&)'unit_test_log.o: In function `void std::__adjust_heap<__gnu_cxx::__normal_iterator<std::pair<boost::unit_test:: basic_cstring<char const>, boost::unit_test::output_format>*, std::vector<std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format> > > >, int, std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format>, boost::unit_test::fixed_mapping<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format, boost::unit_test::case_ins_less<char const> >::p2>(__gnu_cxx::__normal_iterator<std::pair<boost::unit_test::basic_cstrin g<char const>, boost::unit_test::output_format>*, std::vector<std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format> > > >, int, int, std::pair<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format>, boost::unit_test::fixed_mapping<boost::unit_test::basic_cstring<char const>, boost::unit_test::output_format, boost::unit_test::case_ins_less<char const> >::p2)': /usr/include/c++/3.3.2/bits/stl_heap.h:197: undefined reference to `boost::unit_test::ut_detail::msvc65_like_log_formatter::msvc65_like_log_for matter[in-charge] (boost::unit_test::unit_test_log const&)' unit_test_log.o: In function `boost::unit_test::unit_test_log::set_log_format(boost::unit_test::basic_cst ring<char const>)': /usr/local/boost/libs/test/src/unit_test_log.cpp:381: undefined reference to `boost::unit_test::ut_detail::msvc65_like_log_formatter::msvc65_like_log_for matter[in-charge](boost::unit_test::unit_test_log const&)' /usr/local/boost/libs/test/src/unit_test_log.cpp:383: undefined reference to `boost::unit_test::ut_detail::xml_log_formatter::xml_log_formatter[in-charge ](boost::unit_test::unit_test_log const&)' collect2: ld returned 1 exit status Do I need the latest CVS snapshot or what? This worked a few days ago, so I don't know what happened. I'm using the unit test framework. Dave --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.701 / Virus Database: 458 - Release Date: 6/7/2004

2 2

[CVS] Problem
by David B. Held 18 Jun '04

18 Jun '04

cvs update: Updating boost/format/detail cvs update: failed to create lock directory for `/cvsroot/boost/boost/boost/form at/detail' (/cvsroot/boost/boost/boost/format/detail/#cvs.lock): No space left o n device cvs update: failed to obtain dir lock in repository `/cvsroot/boost/boost/boost/ format/detail' cvs [update aborted]: read lock failed - giving up Looks like an SF issue to me. Is this going to get fixed by itself, or should someone send them a note? Dave --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.701 / Virus Database: 458 - Release Date: 6/7/2004

3 2

Re: [boost] program_options with mingw
by Janusz Piwowarski 18 Jun '04

18 Jun '04

Janusz Piwowarski wrote: > BTW, i successfully compile program_options library and examples with > stlport 4.6.2; but my program, where i use boost::thread, don't want to > link. Sorry, i check it now - examples also don't link. Regards, Janusz

2 2