- Boost - lists.boost.org

iterator_adaptor: underlying iterator type?
by Aleksey Gurtovoy 20 May '05

20 May '05

Currently 'iterator_adaptor' exposes its underlying iterator _object_ (through 'base()'), but not its type, which stands in the way of a generic code manipilating adapted iterators/sequences, e.g.: template< typename Sequence > mtn::iterator_range< typename Sequence::iterator::base_type > // ^^^^^^^^^^^ // currently unavailable base_view( Sequence& seq ) { return mtn::make_iterator_range( seq.begin().base() , seq.end().base() ); } Any objections if I add the typedef (and update the docs correspondingly)? -- Aleksey Gurtovoy MetaCommunications Engineering

3 7

Re: [boost] Building from current CVS
by Victor A. Wagner Jr. 20 May '05

20 May '05

At 08:56 2005-05-20, you wrote: > 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. if I remember correctly, the spawn:.... happens when, for some reason, the vcvars32.bat didn't get get called so the environment doesn't get set up properly. btw, exact error messges are useful for us to help track down problems, and in many cases a few lines _before_ the error will help put things in context. >Any ideas for a better way to build the boost libraries? > > >_______________________________________________ >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

Tuples: how to get rid off the open/closing characters??
by Oliver Kullmann 20 May '05

20 May '05

Hello, looking into the code, the documentation, and the proposed standard I can't find a way to output a boost::tuple to a stream with no opening and closing characters??? tuples::tuple_open requires a character, and thus one has to use some opening character, and equally some closing character???? (I can't believe this: Everybody knows that adding strings is much easier than erasing them.) Oliver

2 2

[regex] match_partial and regex_search
by Eric Niebler 20 May '05

20 May '05

I noticed some surprising behavior with match_partial and regex_search. Consider: regex e("abc|b"); string str("ab"); smatch what; if(regex_search(str, what, e, match_default | match_partial)) { cout << (what[0].matched ? "full" : "partial") << '\n'; } This code displays "partial". Clearly, regex_search is bombing out just as soon as it finds a match, partial or otherwise. But in this case, if it kept looking, it would find a full match. My understanding is that full matches are always preferred to partial matches. I couldn't find any discussion about this case in the regex docs or the std proposal. Did I miss it? What's the intention here? Is the std proposal underspecified? -- Eric Niebler Boost Consulting www.boost-consulting.com

3 4

[random] Update for better TR1 compliance
by Jens Maurer 20 May '05

20 May '05

I've checked in changes to the Boost.Random library that add constructors and seeding for both template<class Generator> and unsigned long arguments, thereby moving Boost.Random one step further towards TR1 compliance. The random_test.cpp program now has basic tests for this feature. In order to guide overload resolution, I've used boost::enable_if<> and type traits to make sure that integral arguments don't try to call the "template<class Generator>" overloads. This could mean decreased compiler support, sorry. It works for me with gcc 3.4.3. Jens Maurer

5 7

Interest in C function pointer utility?
by Rene Rivera 20 May '05

20 May '05

In rewriting a plugin interface I use, which for language portability uses C function pointers as the entry points, I came up with a "make_c_function" utility. I use it to translate C++ functions, any of objects, binds, function, members, et. to _real_ C function pointers. For example: class P { public: int foo(int); }; P p; extern "C" { void * get_plugin_call(int n) { if (1 == n) { return make_c_function<P,int(int)>( boost::bind(&p,p::foo,_1)); } else { return 0; } } } [example much abbreviated from real life use] -- -- 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 4

[iostreams] patch for examples/dictionary_filter.hpp for bcc32
by Russell Hind 20 May '05

20 May '05

Please find attached a patch for libs/iostreams/example/dictionary_filter.hpp to help get the tests to build under bcc32 5.6.x and STLPort Thanks Russell Index: libs/iostreams/example/dictionary_filter.hpp =================================================================== RCS file: /cvsroot/boost/boost/libs/iostreams/example/dictionary_filter.hpp,v retrieving revision 1.3 diff -u -r1.3 dictionary_filter.hpp --- libs/iostreams/example/dictionary_filter.hpp 20 May 2005 03:59:33 -0000 1.3 +++ libs/iostreams/example/dictionary_filter.hpp 20 May 2005 12:22:17 -0000 @@ -42,7 +42,11 @@ using namespace std; while (true) { int c = std::cin.get(); +#if defined(__BORLANDC__) && (__BORLANDC__ >= 0x560) && (__BORLANDC__ <= 0x564) && !defined(_USE_OLD_RW_STL) + if (c == EOF || !std::isalpha(c)) { +#else if (c == EOF || !std::isalpha(c, dictionary_.getloc())) { +#endif dictionary_.replace(current_word_); cout.write( current_word_.data(), static_cast<streamsize>(current_word_.size()) ); @@ -84,7 +88,11 @@ if ((c = iostreams::get(src)) == WOULD_BLOCK) return WOULD_BLOCK; +#if defined(__BORLANDC__) && (__BORLANDC__ >= 0x560) && (__BORLANDC__ <= 0x564) && !defined(_USE_OLD_RW_STL) + if (c == EOF || !std::isalpha(c)) { +#else if (c == EOF || !std::isalpha(c, dictionary_.getloc())) { +#endif dictionary_.replace(current_word_); off_ = 0; if (c == EOF) @@ -127,7 +135,11 @@ if (off_ != std::string::npos && !write_current_word(dest)) return false; +#if defined(__BORLANDC__) && (__BORLANDC__ >= 0x560) && (__BORLANDC__ <= 0x564) && !defined(_USE_OLD_RW_STL) + if (!std::isalpha(c)) { +#else if (!std::isalpha(c, dictionary_.getloc())) { +#endif dictionary_.replace(current_word_); off_ = 0; } @@ -190,8 +202,13 @@ if (it == map_.end()) return false; string& value = it->second; +#if defined(__BORLANDC__) && (__BORLANDC__ >= 0x560) && (__BORLANDC__ <= 0x564) && !defined(_USE_OLD_RW_STL) + if (!value.empty() && !key.empty() && std::isupper(key[0])) + value[0] = std::toupper(value[0]); +#else if (!value.empty() && !key.empty() && std::isupper(key[0], loc_)) value[0] = std::toupper(value[0], loc_); +#endif key = value; return true; } @@ -201,7 +218,11 @@ inline void dictionary::tolower(std::string& str) { for (std::string::size_type z = 0, len = str.size(); z < len; ++z) +#if defined(__BORLANDC__) && (__BORLANDC__ >= 0x560) && (__BORLANDC__ <= 0x564) && !defined(_USE_OLD_RW_STL) + str[z] = std::tolower(str[z]); +#else str[z] = std::tolower(str[z], loc_); +#endif } } } } // End namespaces example, iostreams, boost.

2 1

RE: Non-intrusive serialization with VC2003 (7.1) and building from CVS
by Marcin Tustin 20 May '05

20 May '05

It looks a lot like the problem I was having was caused by constness. To be clear, I was doing: template<class Archive> void serialize(Archive & ar, const Jrs::SmartPtr<D2::Message>& g, const unsigned int version) { //... } Now I'm doing: template<class Archive> void serialize(Archive & ar, Jrs::SmartPtr<D2::Message>& g, const unsigned int version) { // ... } The new version does compile, but as I am having problems building boost (from CVS), it doesn't link because the libraries don't exist. It compiles with the CVS version, but still does not compile under 1.32. As to building, I am trying to use the version of bjam I built to build 1.32, running it from the place it was built to: mt@penfold /cygdrive/c/new_boost/boost $ /cygdrive/c/boost_1_32_0/tools/build/jam_src/bin.ntx86/bjam.exe But this cannot create files or directories. Any suggestions?

1 0

[serialization][ptr_container] serialization of ptr_containers
by Felipe Magno de Almeida 20 May '05

20 May '05

Hi, I was trying to serialiaze ptr_containers and I couldnt find a way, so I copied some headers and modified them to serialize ptr_list(the only one I need to serialize in the moment), and it seems to be working. So If someone is interested, I could send it to someone. Im not an expert in the serialize library, so I dont even know if it is really right... But it worked to me(the objects are all serialized as pointers, so if there's two objects then it just serialize one...). I think that extending it to serialize others sequence containers would be very easy, but I didnt touch in the associative containers... The files that I created: ptr_collections_load_imp.hpp // from collections_load_imp.hpp ptr_collections_save_imp.hpp // from collections_save_imp.hpp ptr_list.hpp // from list.hpp Thank you. -- Felipe Magno de Almeida UIN: 2113442 email: felipe.m.almeida+spam at gmail com felipe.almeida+spam at ic unicamp br, felipe.m.almeida at gmail com, felipe+spam at synergy com (Remove the +spam from the email) I am a C, modern C++, MFC, ODBC, Windows Services, MAPI developer from synergy, and Computer Science student from State University of Campinas(UNICAMP). To know more about: Unicamp: http://www.ic.unicamp.br Synergy: http://www.synergy.com.br current work: http://www.mintercept.com "There is no dark side of the moon really. Matter of fact it's all dark."

2 1

Re: [boost] Re: Re: char[] support in Boost.Range
by brangdon＠cix.compulink.co.uk 20 May '05

20 May '05

In-Reply-To: <d6dhiu$hai$1(a)sea.gmane.org> technews(a)kangaroologic.com (Jonathan Turkanis) wrote (abridged): > > Are we going to generalise it to allow any (compile-time constant) > > terminator? > > Why does the terminator have to be a compile-time constant? I was hesitant about suggesting a generalisation which added run-time overhead over only supporting '\0'. Also, the need is not very common in my experience. -- Dave Harris, Nottingham, UK.

3 4