September 2004 - Boost - lists.preview.boost.org

[serialization] request: low-level info about order of serialization
by Joaquín Mª López Muñoz 06 Sep '04

06 Sep '04

I'm slowly designing the addition of serialization support to Boost.MultiIndex, and come up with a need that, AFAIK, the current serialization library does not cover: The serialization of a multi_index_container should ensure that the order in which elements appear is preserved for all indices of the container. This implies serializing the elements and then recording the appropriate rearrangements in each index. I'm writing the code for serializing these rearrangements in an efficient manner as some sort of "diff" sequences, using an algorithm called "longest increasing subsequence" (LIS). The algorithm would greatly benefit for some low-level API by the serialization lib that, given an object reference, would return the order in which that object was serialized. I guess this information is already available internally, as the lib must keep track of previously saved objects. If this requirement is deemed too exotic to provide to the general user, well, I can write something myself without aid from the lib, but I thought I should ask at least :) Thank you, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

1 0

[request] Sun and IBM users...
by Paul Mensonides 06 Sep '04

06 Sep '04

Can someone test the following preprocessor code on the Sun and IBM preprocessors: #include <boost/preprocessor/detail/split.hpp> #include <boost/preprocessor/punctuation/comma.hpp> #include <boost/preprocessor/punctuation/paren.hpp> #include <boost/preprocessor/tuple/eat.hpp> #define IS_NULLARY(x) \ BOOST_PP_SPLIT(1, IS_NULLARY_C x BOOST_PP_COMMA() 0) \ /**/ #define IS_NULLARY_C() \ ~, 1 BOOST_PP_RPAREN() \ BOOST_PP_TUPLE_EAT(2) BOOST_PP_LPAREN() ~ \ /**/ IS_NULLARY(()) // 1 IS_NULLARY(()abc) // 1 IS_NULLARY(+) // 0 IS_NULLARY(xyz) // 0 #define IS_UNARY(x) IS_NULLARY(IS_UNARY_C x) #define IS_UNARY_C(a) () IS_UNARY((a)) // 1 IS_UNARY((a)abc) // 1 IS_UNARY(+) // 0 IS_UNARY(xyz) // 0 Regards and thanks, Paul Mensonides

3 12

algorithm/string bug
by Llew Sion Goodstadt 06 Sep '04

06 Sep '04

There seems to be a bug somewhere in #include <boost/algorithm/string.hpp> If I am not mistaken, this is the central include file for all the string algorithms. But if, e.g. in replace_example.hpp, you replace the separate declarations of #include <boost/algorithm/string/replace.hpp> #include <boost/algorithm/string/erase.hpp> #include <boost/algorithm/string/case_conv.hpp> with //#include <boost/algorithm/string/replace.hpp> //#include <boost/algorithm/string/erase.hpp> //#include <boost/algorithm/string/case_conv.hpp> #include <boost/algorithm/string.hpp> the file no longer compiles. However, #include <boost/algorithm/string/replace.hpp> //#include <boost/algorithm/string/erase.hpp> //#include <boost/algorithm/string/case_conv.hpp> #include <boost/algorithm/string.hpp> does work. Is there an error in the order of header inclusion? Leo Goodstadt

2 1

Program options possible error?
by Llew Sion Goodstadt 06 Sep '04

06 Sep '04

In <boost/program_options/detail/config_file.hpp> why is BOOST_WORKAROUND used (line 19) before the inclusion of #include <boost/detail/workaround.hpp>? Thanks Leo

2 1

RE: [boost] Re: IOStreams formal review start
by Reece Dunn 06 Sep '04

06 Sep '04

Jonathan Turkanis wrote: >I'm starting to think it would be very useful to have a Flushable concept, >which >would allow components to advertise that they can send all buffered data >downstream at any time. I haven't given it much though yet, but I think it >would >allow OuputFilters to be inserted and removed in the middle of processing a >character sequence, as Dietmar suggested. This would make it possible to write a processor for a PDF file that contains several 'stream' objects, each with different filters (LZW compression, ASCII85 encoding, JPEG images, etc.). Regards, Reece _________________________________________________________________ Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo

1 0

tru64cxx65 regression tests temporarily disabled
by Markus Schöpflin 06 Sep '04

06 Sep '04

The regular regression tests for Compaq C++ 6.5 on Tru64 V5.1 have been temporarily disabled. They will be reactivated as soon as possible. Markus

1 0

RE: [boost] Re: New design proposal for boost::filesystem
by Reece Dunn 06 Sep '04

06 Sep '04

Vladimir Prus wrote: >Martin wrote: > > > Vladimir Prus <ghost <at> cs.msu.su> writes: > > The current path implementation doesn't > > allow you to handle more than one type (i.e. winfs or posixfs). You >can't > > store a registrypath in a fs::path since it can't handle a hkey.. root. > >Why? Can't I put literal "HKEY_CURRENT_USER" in boost::path? I don't think he's questioning that, but the case where you can use a HKEY handle as the root, for example: // note: not sure on exact calls HKEY hkCU, hkBase; ::OpenKey( null, "HKEY_CURRENT_USER", &hkCU ); ::OpenKey( hkCU, "software\\microsoft\\windows", &hkBase ); boost::fs::path regwin( hkBase ); // oops: error boost::fs::path spyware = regwin / "CurrentVersion" / "Run" / spyware_app; if( exists( spyware )) // does the registry key exist { // display the value std::cout << "removing: " << boost::fs::get_regval( spyware ) << '\n'; boost::fs::delete( spyware ); // delete the registry entry } Also, iterating through registry entries requires different API calls to that of iterating through files. > >> Actually, I think it is very desired to have boost::path usable in more > >> contexts than the filesystem. For example > >> > >> fs::path base("http://my_site.org"); > >> ..... get_file(base / "foo" / "bar") ..... > >> > >> would be great. But I'm just don't sure this requires all that drastic > >> changes. > > > > Why do you think it is a drastic change? > > Changing operations will not take much time since it is only to move the > > things inside "#ifdef BOOST_POSIX" and "#ifdef BOOST_WINDOWS" into > > separate overloads. > >And #ifdef the overloads ;-) I don't think Win32 API calls can be compiled >on Linux. > >I really think that win32/posix distinction should say as it is. For other >types of path, I'm not sure. I *think* that boost::fs::path can accomodate >all of them. Of course, if you stick URL into boost::fs::path, the name >'native_file_path' becomes questionable ;-) Why not have a class like std::char_traits (e.g. boost::fs::path_traits) that abstracts the API used by path. That way, you can have: template< typename CharT > struct posix_path_api { typedef ... file_handle; typedef ... directory_iterator_handle; static bool exists( file_handle ); static void delete( file_handle ); static directory_iterator_handle get_next( directory_iterator_handle ); }; This would then simplify the Win32/posix API problems and allow for internet_api, winregistry_api, etc. to be included, e.g. boost::fs::path< char, internet_api< char > > boostweb( "http://www.boost-consulting.com/boost" ); Regards, Reece _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

1 0

warning in boost::program_options
by Rodolfo Schulz de Lima 06 Sep '04

06 Sep '04

Hi, I'm using boost::program_options for the first time and noticed that when compiling a program that uses it using gcc's -Wall, it spits out a warning about an unused function parameter: /usr/include/boost-1_32/boost/program_options/value_semantic.hpp:137: warning: unused parameter 'value_store' Can this be corrected? It's just annoying when using -Werror. Since I've seen warnings in other libraries as well, I wonder why those ones aren't being caught in boost's test summary (on the home page). Just adding -Wall to the compiler option would suffice. Regards, rod

2 1

another warning in boost::program_options
by Rodolfo Schulz de Lima 06 Sep '04

06 Sep '04

Oops... another warning: /usr/include/boost-1_32/boost/program_options/detail/value_semantic.hpp:78: warning: unused parameter 'target_type' There might be others...

1 0

Is there any interest in a simple template for streaming in/out primitives and STL Containers of them?
by Boris Kats 05 Sep '04

05 Sep '04

I am using it for some time and hope that other will benefite from it. One file streamline.h will help user to stream out/in an arbitrary item of primitives or STL containers of them. It is very simple to use; just type like this: #include "streamline.h" using namespace hekate; ....... typedef std::pair<std::string, std::vector<int> > element; element one,other; And stream it out as: streamline(cout,one); or stream it in as: streamline(cin,other); . User will find a lot of examples in the streamtest.cpp file at streamline.tar in "Files section". The streaming templates were tested with gcc version 3.3.2, msvc7 and ibm89 c++ compiler. Boris Kats. boriskats(a)yahoo.com __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 1