January 2007 - Boost-users - lists.preview.boost.org

BOOST_CHECK and functions with more than one template parameter
by Rob Caldecott 09 Jan '07

09 Jan '07

I am trying to test a template function that takes two template parameters, and, because of the "comma in macros" compiler issue, I have hit a brick wall. For example: template<typename T1, typename T2> int func(const T1& t1, const T2& t2) { ... } BOOST_CHECK_EQUAL(func<std::string, int>("Test", 1234), 1234); When compiling BOOST_CHECK_EQUAL above, I get an error due to the comma between std::string and int. As this is a function, I cannot use typedef, and trying to #define a workaround also fails (I am using VS2005). Any ideas how I can test template functions with more than one template parameter? Thanks in advance.

3 2

GCC_BIN_DIRECTORY problem
by remi 09 Jan '07

09 Jan '07

hi i cross compile boost but i see that it impossible tu use the correct GCC with the command GCC_BIN_DIRECTORY How can i compile with another gcc ??!! best regards __________________________________________________ Do You Yahoo!? En finir avec le spam? Yahoo! Mail vous offre la meilleure protection possible contre les messages non sollicités http://mail.yahoo.fr Yahoo! Mail

1 0

Re: [Boost-users] [date_time] timezone rules for different years
by Stephen Turner 09 Jan '07

09 Jan '07

> -----Original Message----- > From: Stephen Turner [mailto:sturner@clicktracks.com] > Sent: 04 January 2007 16:02 > To: 'boost-users(a)lists.boost.org' > Subject: RE: [date_time] timezone rules for different years > > [...snip...] > > Actually, I think the hardest part would be populating the > date_time_zonespec.csv file. Is there already a program to > generate that file from the zoneinfo files, or was it done > semi-by-hand? > Of course, an alternative might be for the library to read the actual zoneinfo files, rather than to extend the intermediate zonespec.csv format. I'm not sure which would be better. -- Stephen Turner, Cambridge, UK http://homepage.ntlworld.com/adelie/stephen/ "The internet is a reflection of our society. If we do not like what we see, the problem is not to fix the mirror, we have to fix society." (Vint Cerf)

1 0

Re: [Boost-users] cross compiling boost
by Hughes, James 09 Jan '07

09 Jan '07

If you are cross compiling boost, you don't need to cross compile bjam - just compile it for your host machine (I assume a PC with Windows or Linux). Then use that bjam to cross compile boost with the command line posted earlier. James > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of remi > Sent: 09 January 2007 11:23 > To: boost-users(a)lists.boost.org > Subject: [Boost-users] cross compiling boost > > > hi, > > I have a problem to create bjam with another toolset called > arm-linux-gcc. I use ./build.sh cc > > CC=arm-linux-gcc > > but it dosen't work ... > > > can anyome help me ?? > > Best regards > > __________________________________________________ > Do You Yahoo!? > En finir avec le spam? Yahoo! Mail vous offre la meilleure > protection possible contre les messages non sollicités > http://mail.yahoo.fr Yahoo! Mail > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

2 1

Re: [Boost-users] RE : Re: cross compiling boost for ARM
by Hughes, James 09 Jan '07

09 Jan '07

Yes. > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of remi > Sent: 05 January 2007 17:41 > To: boost-users(a)lists.boost.org > Subject: [Boost-users] RE : Re: cross compiling boost for ARM > > > Thank tou for the anwser ! > > So if i want to cross complie boost, i need boost_1_33_1.tar > and boost-jam package ? > > __________________________________________________ > Do You Yahoo!? > En finir avec le spam? Yahoo! Mail vous offre la meilleure > protection possible contre les messages non sollicités > http://mail.yahoo.fr Yahoo! Mail > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately.

2 1

Re: [Boost-users] boost::serialization fundamental question about "block read/write"
by Gerd Ritter 09 Jan '07

09 Jan '07

Hi Christian, I have looked at the boost::asio implementation. From what I can see it does use boost::serialization but it wraps each object into it's own archive object inside for every time you call async write (from /example/serialization/connection.hpp): void async_write(const T& t, Handler handler) { // Serialize the data first so we know how large it is. std::ostringstream archive_stream; boost::archive::text_oarchive archive(archive_stream); archive << t; This works fine but has a couple major drawbacks: a) for each object to be sent a new archive is created and destroyed (performance) b) none of the pointer tracking and other boost::serialization features are available and c) especially for small objects this will create serious bandwith "bloat" since each archive contains at least a 27byte header. What I want to achieve is to keep the archive open for the duration of the life time of the connection or logical session which may allow for socket reconnects. I will look into using asio for socket handling though. If I can make it work I'll share the code, maybe it can be included in asio which would be good because I wouldn't have to maintain it ;-) Regards, Gerd > Date: Mon, 8 Jan 2007 15:02:34 -0500 > From: "Christian Henning" <chhenning(a)gmail.com> > Subject: Re: [Boost-users] boost::serialization fundamental question > about "block read/write" > To: boost-users(a)lists.boost.org > Message-ID: > <949801310701081202n5533ba61n41e96dd48945817c(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Gerd, I'm sure you know that already. But, have you taken a look at > boost::asio? There is even an example for using the serialization lib > when sending objects over a socket. > > Here a link: > http://asio.sourceforge.net/boost_asio_0_3_7/libs/asio/doc/examples/index.h… > > Just scroll down a bit to the Serialization section. > > Christian > > > On 1/8/07, Gerd Ritter <gerd.ritter(a)googlemail.com> wrote: > > > > Hi, > > > > I have a more fundamental question/inquiry about the serialization library.

1 0

Support for extended Daylight Saving Time in 2007
by Eric Yankowitz 09 Jan '07

09 Jan '07

Been trying to find information describing boost's level of support for the four week Daylight Saving Time extension in the US that will occur this March. (http://geography.about.com/cs/daylightsavings/a/dst.htm) I haven't been able to find very much. A lot of software is having issues and was wondering if Boost was ready for the event? Was able to find these links, which suggested issues: http://sourceforge.net/tracker/index.php?func=detail&aid=1471723&group_id=7… http://sourceforge.net/tracker/index.php?func=detail&aid=1478619&group_id=7… Any idea if these are being resolved? And if any others exist? Thanks, Eric Yankowitz

1 0

Need Help with Using Boost 1.33 w/ .Net 2005
by Allen 09 Jan '07

09 Jan '07

Hello, I'm a newbie to boost & am trying to use the "filesystem" library with .Net 2005. I've gotten boost to compile & produce the following libraries for windows vc-8_0 tool set: (@ bottom of email) The problem I'm having is 2 fold: 1. which ones do I use ( I think I know, but...) 2. I am using C:\boost\lib\boost_filesystem-vc80-mt-1_33_1.lib C:\boost\lib\boost_filesystem-vc80-mt-1_33_1.dll 3. I've got the dll in the directory my executable runs from 4. I'm including the library w/in my project But, every time I run my application, it bombs on the following code: std::cerr << "file selection has changed: Fname/Folder:" << std::endl; Glib::ustring gus_fname = m_filechooserbuttonChooseComponentsFile->get_filename(); std::cerr << "file name:=" << gus_fname << std::endl << std::endl; Glib::ustring gus_fname_foler = m_filechooserbuttonChooseComponentsFile->get_current_folder(); std::cerr << "folder:=" << gus_fname_foler << std::endl << std::endl; m_gusFobComponentsFileFullPath = gus_fname; std::cerr << "using paths..." << std::endl; boost::filesystem::path p(m_gusFobComponentsFileFullPath, boost::filesystem::native); (**** BOMB ****) The variable, m_gusFobComponentsFileFullPath, has the value: C:\projects\cramOSG_console\trunk\CRAMComponents.fob For the life of me, I can not figure out why boost is crashing. An older version of boost works just fine w/ this code and I am wondering if I'm using the correct libraries or perhaps what was compiled is not correct. The error give is not a simple one to debug. The application simply crashes @ the point noted when run. Under the debugger, it simply crashes in a "locked" file and since I'm not using the debug version of the libs, I can't walk into the code. Would someone please help me? Thank you so much ahead of time. I appreciate your advice and comments. --Allen C:\boost\lib\boost_date_time-vc80-mt-gd.lib C:\boost\lib\boost_filesystem-vc80-mt-1_33_1.lib C:\boost\lib\boost_filesystem-vc80-mt.lib C:\boost\lib\boost_filesystem-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_filesystem-vc80-mt-gd.lib C:\boost\lib\boost_iostreams-vc80-mt-1_33_1.lib C:\boost\lib\boost_iostreams-vc80-mt.lib C:\boost\lib\boost_iostreams-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_iostreams-vc80-mt-gd.lib C:\boost\lib\boost_program_options-vc80-mt-1_33_1.lib C:\boost\lib\boost_program_options-vc80-mt.lib C:\boost\lib\boost_program_options-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_program_options-vc80-mt-gd.lib C:\boost\lib\boost_regex-vc80-mt-1_33_1.lib C:\boost\lib\boost_regex-vc80-mt.lib C:\boost\lib\boost_regex-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_regex-vc80-mt-gd.lib C:\boost\lib\boost_serialization-vc80-mt-1_33_1.lib C:\boost\lib\boost_serialization-vc80-mt.lib C:\boost\lib\boost_serialization-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_serialization-vc80-mt-gd.lib C:\boost\lib\boost_signals-vc80-mt-1_33_1.lib C:\boost\lib\boost_signals-vc80-mt.lib C:\boost\lib\boost_signals-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_signals-vc80-mt-gd.lib C:\boost\lib\boost_thread-vc80-mt-1_33_1.lib C:\boost\lib\boost_thread-vc80-mt.lib C:\boost\lib\boost_thread-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_thread-vc80-mt-gd.lib C:\boost\lib\boost_wserialization-vc80-mt-1_33_1.lib C:\boost\lib\boost_wserialization-vc80-mt.lib C:\boost\lib\boost_wserialization-vc80-mt-gd-1_33_1.lib C:\boost\lib\boost_wserialization-vc80-mt-gd.lib C:\boost\lib\libboost_date_time-vc80-mt-1_33_1.lib C:\boost\lib\libboost_date_time-vc80-mt.lib C:\boost\lib\libboost_date_time-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_date_time-vc80-mt-gd.lib C:\boost\lib\libboost_date_time-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_date_time-vc80-mt-s.lib C:\boost\lib\libboost_date_time-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_date_time-vc80-mt-sgd.lib C:\boost\lib\libboost_filesystem-vc80-mt-1_33_1.lib C:\boost\lib\libboost_filesystem-vc80-mt.lib C:\boost\lib\libboost_filesystem-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_filesystem-vc80-mt-gd.lib C:\boost\lib\libboost_filesystem-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_filesystem-vc80-mt-s.lib C:\boost\lib\libboost_filesystem-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_filesystem-vc80-mt-sgd.lib C:\boost\lib\libboost_iostreams-vc80-mt-1_33_1.lib C:\boost\lib\libboost_iostreams-vc80-mt.lib C:\boost\lib\libboost_iostreams-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_iostreams-vc80-mt-gd.lib C:\boost\lib\libboost_iostreams-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_iostreams-vc80-mt-s.lib C:\boost\lib\libboost_iostreams-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_iostreams-vc80-mt-sgd.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-1_33_1.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-gd.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-s.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_prg_exec_monitor-vc80-mt-sgd.lib C:\boost\lib\libboost_program_options-vc80-mt-1_33_1.lib C:\boost\lib\libboost_program_options-vc80-mt.lib C:\boost\lib\libboost_program_options-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_program_options-vc80-mt-gd.lib C:\boost\lib\libboost_program_options-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_program_options-vc80-mt-s.lib C:\boost\lib\libboost_program_options-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_program_options-vc80-mt-sgd.lib C:\boost\lib\libboost_regex-vc80-mt-1_33_1.lib C:\boost\lib\libboost_regex-vc80-mt.lib C:\boost\lib\libboost_regex-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_regex-vc80-mt-gd.lib C:\boost\lib\libboost_regex-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_regex-vc80-mt-s.lib C:\boost\lib\libboost_regex-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_regex-vc80-mt-sgd.lib C:\boost\lib\libboost_serialization-vc80-mt-1_33_1.lib C:\boost\lib\libboost_serialization-vc80-mt.lib C:\boost\lib\libboost_serialization-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_serialization-vc80-mt-gd.lib C:\boost\lib\libboost_serialization-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_serialization-vc80-mt-s.lib C:\boost\lib\libboost_serialization-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_serialization-vc80-mt-sgd.lib C:\boost\lib\libboost_signals-vc80-mt-1_33_1.lib C:\boost\lib\libboost_signals-vc80-mt.lib C:\boost\lib\libboost_signals-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_signals-vc80-mt-gd.lib C:\boost\lib\libboost_signals-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_signals-vc80-mt-s.lib C:\boost\lib\libboost_signals-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_signals-vc80-mt-sgd.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-1_33_1.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-gd.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-s.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_test_exec_monitor-vc80-mt-sgd.lib C:\boost\lib\libboost_thread-vc80-mt-1_33_1.lib C:\boost\lib\libboost_thread-vc80-mt.lib C:\boost\lib\libboost_thread-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_thread-vc80-mt-gd.lib C:\boost\lib\libboost_thread-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_thread-vc80-mt-s.lib C:\boost\lib\libboost_thread-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_thread-vc80-mt-sgd.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-1_33_1.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-gd.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-s.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_unit_test_framework-vc80-mt-sgd.lib C:\boost\lib\libboost_wave-vc80-mt-1_33_1.lib C:\boost\lib\libboost_wave-vc80-mt.lib C:\boost\lib\libboost_wave-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_wave-vc80-mt-gd.lib C:\boost\lib\libboost_wave-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_wave-vc80-mt-s.lib C:\boost\lib\libboost_wave-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_wave-vc80-mt-sgd.lib C:\boost\lib\libboost_wserialization-vc80-mt-1_33_1.lib C:\boost\lib\libboost_wserialization-vc80-mt.lib C:\boost\lib\libboost_wserialization-vc80-mt-gd-1_33_1.lib C:\boost\lib\libboost_wserialization-vc80-mt-gd.lib C:\boost\lib\libboost_wserialization-vc80-mt-s-1_33_1.lib C:\boost\lib\libboost_wserialization-vc80-mt-s.lib C:\boost\lib\libboost_wserialization-vc80-mt-sgd-1_33_1.lib C:\boost\lib\libboost_wserialization-vc80-mt-sgd.lib C:\boost\lib\boost_date_time-vc80-mt-1_33_1.dll C:\boost\lib\boost_date_time-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_filesystem-vc80-mt-1_33_1.dll C:\boost\lib\boost_filesystem-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_iostreams-vc80-mt-1_33_1.dll C:\boost\lib\boost_iostreams-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_program_options-vc80-mt-1_33_1.dll C:\boost\lib\boost_program_options-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_regex-vc80-mt-1_33_1.dll C:\boost\lib\boost_regex-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_serialization-vc80-mt-1_33_1.dll C:\boost\lib\boost_serialization-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_signals-vc80-mt-1_33_1.dll C:\boost\lib\boost_signals-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_thread-vc80-mt-1_33_1.dll C:\boost\lib\boost_thread-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_wserialization-vc80-mt-1_33_1.dll C:\boost\lib\boost_wserialization-vc80-mt-gd-1_33_1.dll C:\boost\lib\boost_date_time-vc80-mt-1_33_1.lib C:\boost\lib\boost_date_time-vc80-mt.lib C:\boost\lib\boost_date_time-vc80-mt-gd-1_33_1.lib -- Sincerely, Allen Gene Allen Saucier, Jr Senior Software Engineer CAS, Inc 100 Quality Circle Huntsville, AL 35806 or PO Box 11190 Huntsville, AL 35814 (256) 922-6453 (w) "As for I and my house, we shall follow the Lord" Joshua 25:14

2 1

Re: [Boost-users] [Test] Auto test timeouts?
by Sohail Somani 08 Jan '07

08 Jan '07

> [mailto:boost-users-bounces@lists.boost.org] On Behalf Of > Gennadiy Rozental > > "Sohail Somani" <s.somani(a)fincad.com> wrote in message > news:1C1EBEF8DBACDC439D038EA051674EC7567695@xbox.financialcad.com... > > Good morning/afternoon/evening good people of the Boost lists, > > > > Does anyone know how to set timeouts on the auto testing > suite of the > > Boost unit test framework? I'm guessing that I'll need to > write my own > > test_main() but if anyone knows of a way to tweak the auto > test suite in > > general, that would be very useful! > > There is no interface to specify the timeout for > automatically registered > test case. For this test case you will have to use manual > registration. Thanks! And thanks for a great lib btw.

1 0

boost::serialization fundamental question about "block read/write"
by Gerd Ritter 08 Jan '07

08 Jan '07

Hi, I have a more fundamental question/inquiry about the serialization library. What I want to do is to use the serialization library to send classes over a socket. Even though archives are not supposed to be used at streams I figured that it should be possible to create a oarchive on the sender side, create a iarchive on the receiver side, and use these for multiple, successive write / read operations in block mode. In order to test that assumption I created a test program to see if it would be possible. Here the pseudo code: void sync_streams(stringstream &os, stringstream& os) { // write data from one sting stream to the other // this emulates sending the data on a socket int rd_avail = os.tellp() - os.tellg(); os.read(buffer, rd_avail); is.write(buffer, rd_avail); } stringstream os, is; boost::archive::text_oarchive oa(os); sync_streams(os, is); // sync preamble boost::archive::text_iarchive ia(is); oa << object1; sync_streams(os, is); // sync object block ia >> rdObject1; oa << object2; sync_streams(os, is); // sync object block ia >> rdObject2; While I made this work, I wonder if it is a hack or if this is a valid use case for the serialization library. I looked at the asio projects example/source, there it was done by using a full archive for each object to be transmitted. Sending an archive every time seems a bit expensive too me, since a full preamble is sent everytime and I would loose all the pointer tracking and other great features from the serialization library. Regards, Gerd

3 2

[Test] Auto test timeouts?
by Sohail Somani 08 Jan '07

08 Jan '07

Good morning/afternoon/evening good people of the Boost lists, Does anyone know how to set timeouts on the auto testing suite of the Boost unit test framework? I'm guessing that I'll need to write my own test_main() but if anyone knows of a way to tweak the auto test suite in general, that would be very useful! Thanks, Sohail

2 1

Performance problem in iostreams::stream
by Jerker Öhman 08 Jan '07

08 Jan '07

We use iostreams::stream to read from a legacy file format. The code that reads from the stream looks a little like this: void ReadStuff(std::istream &stream, Stuff &stuff, OtherStuff &otherStuff) { StreamDirectory streamDir; stream >> streamDir; stream.seekg(streamDir.GetOffset(STUFF_TAG)); stream >> stuff; stream.seekg(streamDir.GetOffset(OTHER_STUFF_TAG); stream >> otherStuff; } I.e. the stream contains a directory that holds information about the items following the directory and the offsets to them. The stream and code is also organized so that the calls to seekg in most cases are to the current position of the stream. In other words, seekg doesn’t have to do anything. If the stream is buffered the code runs into serious performance problems. After a while seekg ends up in this function. template<typename T, typename Tr, typename Alloc, typename Mode> typename indirect_streambuf<T, Tr, Alloc, Mode>::pos_type indirect_streambuf<T, Tr, Alloc, Mode>::seek_impl (stream_offset off, BOOST_IOS::seekdir way, BOOST_IOS::openmode which) { if (pptr() != 0) this->BOOST_IOSTREAMS_PUBSYNC(); // sync() confuses VisualAge 6. if (way == BOOST_IOS::cur && gptr()) off -= static_cast<off_type>(egptr() - gptr()); setg(0, 0, 0); setp(0, 0); return obj().seek(off, way, which, next_); } and as far as I can see it just dumps the internal buffer and passes the call on. After still some calls we end up in the stream source seek function. This wouldn’t be so bad if it wasn’t for the fact that the stream source offset isn’t the same as the streams offset since the stream is buffered. Perhaps a little example would clarify this. Assume that we read 4 bytes from a stream with a 10k buffer. The stream will then fill its buffer from the underlying source which means that after the read, the stream will have a full 10k buffer and an offset into the buffer that is 4. The underlying stream source will have an offset pointer that points to 10k+1 bytes into the underlying stream. If we now call seekg to position the file to offset 4 (which already is the current position), the stream throws away it’s buffer and we end up in the stream source who’s file position is 10k+1 so it also throws away it’s internal buffers and seeks back in the underlying stream to offset 4. In this way, what should have been a NULL operation turns into something very time-consuming. Previously we used a class that inherited directly from std::basic_streambuff that contained horrible code that no one really understood so switching to boost::iostreams was a blessing. Unfortunately the boost::iostreams implementation is 10 times slower when it is buffered and 50% slower when it is unbuffered. When reading files that are a couple of GB that really matters. /Jerker

1 0

[BGL] how to extract subgraph from existing graph?
by Ferng, Andrew D 08 Jan '07

08 Jan '07

I've got an overall adjacency_list built and ran connected_componets on it. >From this output, I want to do more analysis on the subgraphs found. Is there a slick way to create a new sub adjacency_list by just giving the subset of vertex IDs? template <class EdgeIterator> adjacency_list(EdgeIterator first, EdgeIterator last, vertices_size_type n, edges_size_type m = 0, const GraphProperty& p = GraphProperty()) This looks like the closest one but it requires redefining the edges? Thanks!

2 3

Re: [Boost-users] operators << and >> on boost serialization
by Pfligersdorffer, Christian 08 Jan '07

08 Jan '07

> Ok! > I'm starting to freaking out, because I just can't figure it out some > compilation errors when trying to use the boost serialization library. > I just can't manage what I'm doing wrong. > Ok, I think that the best way to translate my problem is to post the > code and the changes I'm trying to do: > So ans as you can see on the attached file: > My project and all of my classes are inside a namespace the > FlowEngine. > > I have 3 classes: A; B and C to test the boost serialization. > > As it is now it compiles and runs good. > > But I take the comments of class A to split member serialization, just > doing that I get this errors when compiling: > > \3rdparty\include\boost\serialization\access.hpp(93) : error C2662: > 'void FlowEngine::A::save<Archive>(Archive &,const unsigned int)' : > cannot convert 'this' pointer from 'const FlowEngine::A' to > 'FlowEngine::A &' Hi Miguel! I am guessing: when saving you need a const object, that is your member function save() must be const. I'd check on some missing const and probably also would try to use '&' instead of '<<'. Also: do you use the BOOST_SPLIT_BLABLA-macro? Hope this helps you until some geek gives a thourough statement ;-) DI Christian Pfligersdorffer Software Engineering EOS GmbH

1 0

[Boost.Array] gcc 4.1.2 vs. boost alignment
by Robert Mecklenburg 08 Jan '07

08 Jan '07

I've just upgraded my compiler to gcc 4.1.2 and tried the latest implementation of tr1 included with gcc. I've discovered the gcc array implementation is not what I expect: #include <boost/array.hpp> #include <tr1/array> #include <iostream> int main(int , char **) { boost::array<char, 6> barray; std::cout << sizeof(barray) << std::endl; std::tr1::array<char, 6> tr1array; std::cout << sizeof(tr1array) << std::endl; } When run this code produces: g++ foo.cpp && ./a.out 6 16 That is, the boost array is exactly the size I require 6 bytes, but the tr1 array is larger, 16 bytes. I believe this is due to the following declaration in 4.1.2/tr1/array: // Support for zero-sized arrays mandatory. value_type _M_instance[_Nm ? _Nm : 1] __attribute__((__aligned__)); The boost version is not aligned, but the gcc version is. Does the tr1 implementation require the alignment? If so, it appears that tr1::array is definitely not a suitable wrapper for C-style arrays since they aren't the same size! What's the scoop? Thanks, -- Robert

3 2

[BOOST.TEST] [BOOST.WARN] Output weirdness
by Peter 08 Jan '07

08 Jan '07

Hi, I am new to Boost.Test so not sure if this is expected behaviour or not. Based on this minimal test: |----------------------------8←------------------------------------| #include <boost/test/unit_test.hpp> using boost::unit_test::test_suite; // most frequently you implement test cases as a free functions void my_test() { int i=2; BOOST_WARN( sizeof(int) == sizeof(short) ); BOOST_CHECK( i == 1 ); BOOST_REQUIRE( i > 5 ); BOOST_CHECK( i == 6 ); // will never reach this check } test_suite* init_unit_test_suite( int, char* [] ) { test_suite* test= BOOST_TEST_SUITE( " Test Suite!" ); // this example will pass cause we know ahead of time number of expected failures test->add( BOOST_TEST_CASE( & my_test ), 0 /* expected one error */ ); return test; } |----------------------------8←------------------------------------| Taken from this url: http://tinyurl.com/t54th (Click on BOOST_WARN). I expect to see this output (as mentioned at the above link): c:/development/code/practice/ test/mytest.cpp (14) : warning in test_main: condition sizeof(int) == sizeof(short) is not satisfied c:/development/code/practice/ test/mytest.cpp (15) : error in test_main: test i==1 failed c:/development/code/practice/ test/mytest.cpp (16) : fatal error in test_main: test i>5 failed But I see this output Running 1 test case... c:/development/code/practice/ test/mytest.cpp(15): error in " my_test ": check i == 1 failed c:/development/code/practice/ test/mytest.cpp (16): fatal error in " my_test ": critical check i > 5 failed *** 2 failures detected (2 failures expected) in test suite "Master Test Suite" It seems that the BOOST_WARN is not outputting a message. Is this expected behaviour? Also another minor point in the code I have named the BOOST_TEST_SUITE “Test Suite!” but in the output it is calling it “Master Test Suite”. Is this something I am not setting right? Thanks, Peter.

2 1

Re: [Boost-users] Boost-users Digest, Vol 1140, Issue 1
by Peter 08 Jan '07

08 Jan '07

Hi Rob, Thanks for that answer! I eventually stumbled on this URL: http://tinyurl.com/ylpjtl which helped. Following the example I then did it this way: test->add( BOOST_TEST_CASE( boost::bind( &default_ctor_param, argv, argc ) ), 0); I will have to have a think on which way is the better way. Do you have any views on the Pro's and Con's using BOOST_AUTO_TEST_CASE and manually adding it using the test_suite->add method? Thanks for the help, Peter. > ------------------------------ > > Message: 7 > Date: Sun, 7 Jan 2007 11:08:54 +0000 (UTC) > From: Rob Caldecott <robert.caldecott(a)gmail.com> > Subject: Re: [Boost-users] [Boost.test] [BOOST_AUTO_TEST_CASE] > accessing argc and argv > To: boost-users(a)lists.boost.org > Message-ID: <loom.20070107T120734-337(a)post.gmane.org> > Content-Type: text/plain; charset=us-ascii > > Peter <pjfoley <at> bigpond.com> writes: > > > is it possible to access argc and argv? > > I had the same problem. You can use > boost::unit_test::auto_unit_test_suite()->argc and > boost::unit_test::auto_unit_test_suite()->argv. > > Regards.

2 1

[Boost.test] [BOOST_AUTO_TEST_CASE] accessing argc and argv
by Peter 08 Jan '07

08 Jan '07

Hi, I am trying to learn to use the Boost.Test framework and have read through the online documents explaining how to use Boost.Test. I have been unable to find how to access the argc and argv variables while using BOOST_AUTO_TEST_CASE with "BOOST_AUTO_TEST_MAIN" defined. So my question is using "The automatic registration facility" (http://tinyurl.com/y2en48) is it possible to access argc and argv? If not does that mean I have to define a "boost::unit_test::test_suite* init_unit_test_suite ( int argc, char* argv[] )" and use these variables? Thanks, Peter.

3 2

[labmda & function] strange assembly errors with an unsupported compiler
by Server Levent Yilmaz 07 Jan '07

07 Jan '07

Hi All, This is an anomaly I experienced with Portland Group C++ compiler. Well OK, Boost doesn't support this compiler... But so far for Lambda and Function libraries I was able to run all of the tests in the 1-33-1 distribution with success, and it seems pgCC is doing a real good job. There is this one exception though: pgCC generates assembly errors on this arguably weird code that I have. gcc, msvc and hpCC worked fine... So obviously this seems to be an issue for PG itself and not Boost; but the code under question is really a bit weird and I am not 100% sure if it is correct use of boost or even C++. Before I carry on with bug reports to PG I'd like to ask for your suggestions on it... Here is the code. Briefly, a boost::function is being passed to some function template that expects a functor to apply on its second argument. Another level of indirection is added where the boost::function itself is generated from a lambda expression inside another function. I wasn't able to narrow it down any further.. (highlighted code is here: http://rafb.net/p/28TknK25.html) (compiler error messages follow) // ======================================== #include <boost/function.hpp> #include <boost/lambda/lambda.hpp> #include <boost/lambda/bind.hpp> #include <boost/lambda/casts.hpp> #include <iostream> // Some struct of only double members struct A { double a; double b; }; // The "complicated" function that expect a functor to // operate on an instance of A template< class Func > void foo(const Func& f, const A& a) { std::cout << f(a) << std::endl; } // A function object generator. // It returns a functor which in turn returns some // double member of A accessed via address offset boost::function<double(const A&)> getmem ( const A* obj, const double* mem ) { ptrdiff_t shift = mem - reinterpret_cast<const double*>(obj); using namespace boost::lambda; return *(ll_reinterpret_cast<const double*>(&_1) + constant(shift) ); } // int main() { A obj; obj.a = 1.; obj.b = 2.; // foo( getmem(&obj, &obj.b), obj ); return 0; } // wherever this compiles, it prints out "2". // ========================================== Here is the compiler output: PGCC-W-0155-No va_start() seen (/opt/pgi/6.1.4/linux86-64/6.1/include/CC/iostream: 689) PGCC/x86 Linux/x86-64 6.1-4: compilation completed with warnings /tmp/pgCCbaaaasxqap.s: Assembler messages: /tmp/pgCCbaaaasxqap.s:2499: Error: junk `(%rbx)' after expression /tmp/pgCCbaaaasxqap.s:2500: Error: junk `(%rbx)' after expression The assembly lines under question is pasted here: http://rafb.net/p/LW5IX765.html -- lines 7 and 8. The va_start() warning is probably irrelevant (this is not the only place I have seen it, and never failed before with these warnings) any guidance will be appreciated, thanks -- Server Levent Yilmaz Mechanical Engineering @ PITT

2 3

[Boost.Serialization] St8bad_cast during serialization
by sadrok 07 Jan '07

07 Jan '07

Hi, This would be my first post here. Needless to say I'm relatively a newbie when it comes to using Boost. I've recently decided to look into using Boost to ease some tasks in my future programming projects. I've stumbled upon Boost.Serialization and was amazed at the ease and power it provides. I've decided to use this to replace a hand-wrapped serialization library I created for a project I'm involved with since I foresee in the future more difficult serialization tasks that my library wouldn't be able to handle. So far so good, but during replacing my code with Boost.Serialization and going through various static asserts I've come to a obstacle I cannot figure out. My application saves message classes derived from a Message base class (it has a virtual deconstructor) and sends this serialized data over a UNIX socket for IPC between interconnected processes. The sending side seems to work fine as can be seen from the debugging output below: In base/module.cpp line 111 function SendMessage : [ 22 serialization::archive 3 4 core 10 LogMessage -1209954316 1 18 Sadrok::LogMessage 1 0 0 0 1168098092 55 Loaded module log from file modules/liblog.so pid 14250 ] However on the receiving side I have this: ia & BOOST_SERIALIZATION_NVP(msginfo.msg); which ends up throwing an bad_cast exception Unhandled exception: St8bad_cast msginfo.msg is Message* I even tried loading into a LogMessage * with the same error. I have (in the logmessage header) BOOST_CLASS_EXPORT for the LogMessage (otherwise Boost would've thrown unregistered_class while saving). I can provide more information although I wouldn't know what else to post. Generally I'd like to know if anyone has any idea why I'm getting the bad_cast exception, where it gets thrown, or at least how to figure out where the problem exists so I can fix it. Thank you Sadrok sadrok.za(a)gmail.com Yahoo! IM: sadrok_za Jabber ID: sadrok(a)jabber.obsidian.co.za

3 9

How to build boost library's document
by Bo Yang 07 Jan '07

07 Jan '07

Hi, I download the boost source code from the CVS repository, and build it with bjam. Only found that there is no document builded in the libs directory. How to build boost library's document?

3 3

Re: [Boost-users] Boost-users Digest, Vol 1140, Issue 1
by Peter 07 Jan '07

07 Jan '07

Hi, Sorry I forgot to add that I am using RC_1_34_0 version updated from this morning. Thanks, Peter > > Message: 6 > Date: Sun, 7 Jan 2007 18:25:34 +1100 > From: "Peter" <pjfoley(a)bigpond.com> > Subject: [Boost-users] [BOOST.TEST] [BOOST.WARN] Output weirdness > To: <boost-users(a)lists.boost.org> > Message-ID: <000701c7322d$04f85850$1100a8c0(a)Billswan.local> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I am new to Boost.Test so not sure if this is expected behaviour or not. > > Based on this minimal test: > > |----------------------------8?------------------------------------| > #include <boost/test/unit_test.hpp> > using boost::unit_test::test_suite; > > // most frequently you implement test cases as a free functions > void my_test() > { > > int i=2; > BOOST_WARN( sizeof(int) == sizeof(short) ); > BOOST_CHECK( i == 1 ); > BOOST_REQUIRE( i > 5 ); > BOOST_CHECK( i == 6 ); // will never reach this check > } > > test_suite* > init_unit_test_suite( int, char* [] ) { > test_suite* test= BOOST_TEST_SUITE( " Test Suite!" ); > > // this example will pass cause we know ahead of time number of > expected failures > test->add( BOOST_TEST_CASE( & my_test ), 0 /* expected one error */ ); > > return test; > } > |----------------------------8?------------------------------------| > > Taken from this url: http://tinyurl.com/t54th (Click on BOOST_WARN). > > I expect to see this output (as mentioned at the above link): > > c:/development/code/practice/ test/mytest.cpp (14) : warning in test_main: > condition sizeof(int) == sizeof(short) is not satisfied > c:/development/code/practice/ test/mytest.cpp (15) : error in test_main: > test i==1 failed > c:/development/code/practice/ test/mytest.cpp (16) : fatal error in > test_main: test i>5 failed > > But I see this output > > Running 1 test case... > c:/development/code/practice/ test/mytest.cpp(15): error in " my_test ": > check i == 1 failed > c:/development/code/practice/ test/mytest.cpp (16): fatal error in " > my_test ": critical check i > 5 failed > > *** 2 failures detected (2 failures expected) in test suite "Master Test > Suite" > > It seems that the BOOST_WARN is not outputting a message. Is this > expected behaviour? > > Also another minor point in the code I have named the BOOST_TEST_SUITE > ?Test Suite!? but in the output it is calling it ?Master Test Suite?. Is > this something I am not setting right? > > Thanks, > > Peter. >

1 0

boost signals, boost bind, visit_each + gcc 4.1 = broken ?
by Koen Deforche 06 Jan '07

06 Jan '07

All, I encountered a problem using boost signals, with gcc 4.1.1 although all is fine using gcc 3.4.4. I am using boost 1.33.1. I get an error which terminates with: /usr/include/boost/bind.hpp: In function 'void boost::visit_each(V&, const boost::_bi::value<T>&, int) [with V = boost::signals::detail::bound_objects_visitor, T = AlignmentWidget*]': /usr/include/boost/bind.hpp:239: instantiated from 'void boost::_bi::list1<A1>::accept(V&) const [with V = boost::signals::detail::bound_objects_visitor, A1 = boost::_bi::value<AlignmentWidget*>]' /usr/include/boost/bind/bind_template.hpp:150: instantiated from 'void boost::_bi::bind_t<R, F, L>::accept(V&) const [with V = boost::signals::detail::bound_objects_visitor, R = void, F = boost::_mfi::mf0<void, AlignmentWidget>, L = boost::_bi::list1<boost::_bi::value<AlignmentWidget*> >]' /usr/include/boost/bind.hpp:1213: instantiated from 'void boost::visit_each(V&, const boost::_bi::bind_t<R, F, L>&, int) [with V = boost::signals::detail::bound_objects_visitor, R = void, F = boost::_mfi::mf0<void, AlignmentWidget>, L = boost::_bi::list1<boost::_bi::value<AlignmentWidget*> >]' /usr/include/boost/visit_each.hpp:25: instantiated from 'void boost::visit_each(Visitor&, const T&) [with Visitor = boost::signals::detail::bound_objects_visitor, T = boost::_bi::bind_t<void, boost::_mfi::mf0<void, AlignmentWidget>, boost::_bi::list1<boost::_bi::value<AlignmentWidget*> > >]' /usr/include/boost/signals/slot.hpp:121: instantiated from 'boost::slot<SlotFunction>::slot(const F&) [with F = boost::_bi::bind_t<void, boost::_mfi::mf0<void, AlignmentWidget>, boost::_bi::list1<boost::_bi::value<AlignmentWidget*> > >, SlotFunction = boost::function0<void, std::allocator<boost::function_base> >]' /usr/local/include/WSignal:603: instantiated from 'boost::signals::connection Wt::EventSignal<void>::connect(T*, void (T::*)()) [with T = AlignmentWidget]' /home/kdforc0/project/c++/sequencetool/src/web/AlignmentWidget.C:59: instantiated from here /usr/include/boost/bind.hpp:1208: error: no matching function for call to 'visit_each(boost::signals::detail::bound_objects_visitor&, AlignmentWidget* const&, int)' Since AlignmentWidget inherits indirectly from boost::signals::trackable, this specialisation should really exist ? Is this is a bug in gcc 4.1.1 or with boost ? Is there a workaround for making it work with gcc 4.1.1 ? Regards, koen

2 1

Re: [Boost-users] Mapping from type to value (Ovanes Markarian)
by Johan Torp 06 Jan '07

06 Jan '07

Wow, two perfect answer in such a short time! Thanks a lot. Are there more parts of MPL that are undocumented? When I've learned more about MPL I wouldn't mind helping to document some parts of it. It's probably a good way to learn it too :) Best Regards, -- System Developer TouchTable AB Tel: +46 (0)31 773 68 12 johan.torp(a)touchtable.se

3 2

portland group compilers (pg++, pgi, pgCC)
by Server Levent Yilmaz 05 Jan '07

05 Jan '07

Hi All, Please correct me if this is off topic here.. I sadly realized that there is no compiler toolset available for Portland Group Compilers (http://www.pgroup.com/) Before submitting an entry in the Support Request, and digging in (probably REALLY deep), I was wondering if there is anyone that has any experience with these compilers (failure or success, *nix or win), particularly for the following libraries: serialization multi_array bind lambda filesystem thank you, levent

3 4