- Boost - lists.boost.org

[1.33 release] pdf doc generation
by Jeff Garland 26 Apr '05

26 Apr '05

I'm not sure who to ask, so I'll just throw this out there. For the 1.33 release I'd like to fix whatever it was that kept date-time docs from being included from the 1.32 pdf file. I don't think there was a full accounting after 1.32 as to what stopped date-time from being included. Given that I am still unable to generate a full boost pdf (fails in the fo processing step) I'm not really able to help diagnose and fix the problem. I'm aware that this works for others, so there's something wrong with my setup... So here's what would be really helpful: 1) whomever is going to generate the pdf docs would generate and post a pre 1.33 version soon 2) if there is a problem with date-time we can work on correcting it 3) we can re-run at least once a week as we put release doc changes in Thx, Jeff

2 2

GOOD DAY
by witt＠acm.org 26 Apr '05

26 Apr '05

Mail transaction failed. Partial message is available.

1 0

[iostreams] error in docs
by JOAQUIN LOPEZ MU?Z 26 Apr '05

26 Apr '05

The main page of Boost.Iostreams docs says "Note: This library has been accepted as part of Boost, but is not part of the current Boost distribution..." I understand this disclaimer should now be removed. Joaquín M López Muñz Telefónica, Investigación y Desarrollo

2 1

how to use boost in VC6
by sanduoren 25 Apr '05

25 Apr '05

I'm a learner of boost.But the boost make me head ache.for example, I can't use /boost/algorithm/string.The VC6 compiler gives hints: yes_no_type.hpp(22) : error C2265: '<Unknown>' : reference to a zero-sized array is illegal yes_no_type.hpp(23) : see reference to class template instantiation 'boost::algorithm::size_descriptor<I>' being compiled who can tell me how to use boost in VC6

9 10

Re: Logging Library -- Formal Review
by Tom Brinkman 25 Apr '05

25 Apr '05

Thanks for your submission John. I've added your library to the review queue. Contact my private email to make further arrangements about a review manager and review start date. If you feel that it is ready, we should be able to get it reviewed within the next month or two. Tom Brinkman reportbase(a)gmail.com Boost Review Wizard

2 1

Re: [boost] Re: [network] An RFC - updated
by Iain Hanson 25 Apr '05

25 Apr '05

On Sun, 2005-04-24 at 14:13 -0700, Don G wrote: > Hi Peter, > > Can you give an example of a developer that absolutely > > insists on a single-threaded implementation (not > > interface)? > > I think Iain Hanson is that camp. Could be wrong. > Yes. To support platform that do not have preemptive multi-tasking. /ikh

1 0

Re: [boost] Re: [network] An RFC - updated
by Iain Hanson 25 Apr '05

25 Apr '05

On Mon, 2005-04-25 at 00:50 +0300, Peter Dimov wrote: > Don G wrote: > >> This doesn't make any of these streams networks, > >> and neither is a communication port a network. > > > > I won't debate semantics here (too much<g>): Once the line is up, > > communications between A and B occur in exactly the same way as they > > would with TCP/IP. Both ends "listen" for incoming stream connections > > on multiple ports (each for a different "service"), each can accept > > one or more datagrams on different ports, again for different > > services. In a nutshell, they are abstractly identical. The big > > difference is that the entire network consists of two hosts. > > Yes, I see. I was thinking of a different scenario, however, one in which > you communicate with a device over a serial line (not with another host) > using a specified protocol. Since serial lines are relatively slow, > asynchronous communication is a good thing. > > >> This of course leads to the obvious question: > >> which network gives me a stream over COM1? > > > > network_ptr com1 = > > new net_over_stream( > > new stream_over_serial("com1")); > > Wait a minute. Which network creates the stream_over_serial? Assume that I > don't need the outer network since I'll be communicating with a printer, for > example. > > >> LPT1? > > > > network_ptr lpt1 = > > new net_over_stream( > > new stream_over_lpt("lpt1")); This is wrong IMHO. These are devices. If you want to implement a network over them then it should be done with device drivers. E.g you could implement PPP over COMn and then access it via socket or net:: lib via TCP or UDP. /ikh

1 0

boost::function and boost::serialize
by mysticdevil＠gmail.com 25 Apr '05

25 Apr '05

I would like to be able to serialize boost::function objects with the boost::serialize library, and i really don't know anything about the internal structure of boost::function nor how it works, and when trying to read the headers i really get lost there. So could anyone give me a hint or something on how to make a wrapper for boost::function (i know that function address might change from executable to executable, and also for run to run, that's why i thought "adding" a translator, that i assing a name to each function i have a pointer to, and when it serializes it it saves the name, and when loading, it search the address of the function with that name)... if you know how this could be done, or have any hint i will greatly appreaciate it... Also i would like to know how boost::serialize handles the shared pointers, because i my own designed objects with reference counting, and i don't know how to serialize them (to preserve shared behavior), and also i have the doubt, what happens, if i have an object shared 8 times in memory, and i only serialize it 4 times, so when i load it again, the counter will say 8 or 4?. Thanks you very much...

1 0

Re: [boost] Re: [network] An RFC - updated
by Iain Hanson 25 Apr '05

25 Apr '05

On Sun, 2005-04-24 at 17:45 -0700, Don G wrote: > Hi Mats, > > It's good to have someone with experience in non-TCP environments! > Glad you're here. > > > The X.25 API doesn't provide the equivalent to the tcp > > listen(2) backlog parameter. To drive an X.25 acceptor > > to be capable of accepting incoming calls at a high > > rate, one has to implement the backlog oneself. This is because you are doing this in the wrong place IMHO. ( see below ). > > Perhaps this is something that should be part of the impl of the > acceptor for X.25. That would make X.25 and TCP the same in this > sense (there are no doubt other differences of which this is just > one). No. You are comparing apples and oranges. TCP is a transport layer protocol and X.25 is predominantly a Network layer protocol. A connection Oriented equivalent to IP. The correct place to do this is with a device driver 99.9% of the time. /ikh

1 0

[threads] read_write_mutex performance
by Peter Dimov 25 Apr '05

25 Apr '05

What are the design goals of read_write_mutex? (Lock proliferation aside for a moment.) My understanding has always been that read/write locks are an optimization, that is, a read/write lock-based algorithm should deliver better performance than the same algorithm with "ordinary" locks. Right? Wrong. The program at the end of this message demonstrates that in this specific (contrived?) case ordinary mutexes outperform a read/write mutex by a factor of 2.5 or more in almost every scenario, even when no writers are active! In some scenarios (16 readers, 4 writers, 10,000,000 iterations) the ordinary mutex case completes in under 8 seconds on my machine, but the read/write case exceeded my patience threshold. Am I missing something? -- Peter Dimov http://www.pdimov.com #include <boost/thread.hpp> #include <boost/thread/read_write_mutex.hpp> #include <iostream> #include <vector> #include <time.h> //#define RWLOCK int const n = 1000000; int const n_readers = 16; int const n_writers = 0; std::vector<int> v; #ifdef RWLOCK boost::read_write_mutex mtx( boost::read_write_scheduling_policy::alternating_many_reads ); #else boost::mutex mtx; #endif void reader_thread() { int m = 0; for( int i = 0; i < n; ++i ) { #ifdef RWLOCK boost::read_write_mutex::scoped_read_lock lock( mtx ); #else boost::mutex::scoped_lock lock( mtx ); #endif m += v[ i ]; } std::cout << m << std::endl; } void writer_thread() { for( int i = 0; i < n; ++i ) { #ifdef RWLOCK boost::read_write_mutex::scoped_write_lock lock( mtx ); #else boost::mutex::scoped_lock lock( mtx ); #endif v[ i ] += i; } } int main() { v.resize( n ); boost::thread_group group; clock_t t = clock(); for( int i = 0; i < n_writers; ++i ) { group.add_thread( new boost::thread( writer_thread ) ); } for( int i = 0; i < n_readers; ++i ) { group.add_thread( new boost::thread( reader_thread ) ); } group.join_all(); t = clock() - t; std::cout << static_cast<double>( t ) / CLOCKS_PER_SEC << '\n'; }

5 5