- Boost - lists.boost.org

Re: [boost] [thread] monotonic xtime
by Matt Doyle 10 Apr '06

10 Apr '06

> -----Original Message----- > [mailto:boost-bounces@lists.boost.org]On Behalf Of Olaf van der Spek > On 4/10/06, Matt Doyle <mdoyle(a)a-m-c.com> wrote: > > I'd like to second that request, needing to use the win32 > Sleep just kills the portability. My workaround for yielding is - > > > > #if defined _MSC_VER || WIN32 > > # include <windows.h> // for Sleep > > # define MILLI_SECOND_SLEEP(value) (Sleep(value)) > > #else > > # include <unistd.h> // for usleep > > # define MILLI_SECOND_SLEEP(value) (usleep(value * 1000)) > > #endif > > > > but that's just a hack, it really should be in the library. > > Isn't yielding itself a hack? > Shouldn't thread coordination be used instead? If you're waiting for another thread to do something I'd agree. What I run into all the time though is that I want to poll a device every so often so I want to surrender my thread for x amount of time. Scanned by McAfee GroupShield {X3BTB534}

1 0

Using serialization for replication
by prez＠neuromancy.net 10 Apr '06

10 Apr '06

Hey, I want to use serialization for some kind of active replication, however the biggest barrier to this is the fact that serialization does not allow me to put the same object into the stream twice. To be more precise, I want to be able to serialize both to a network and to disk, and I very much like the elegance of the serialization approach (plus the fact it can re-create pointer references, arrays, and such). So my questions are: a) How difficult would it be to be able to allow an object to be serialized twice, where the second copy would more or less do an operator= (instead of creating a new object) on the first copy on deserialization. b) How difficult would it be to have more or less an 'appending' serialization stream - ie. I deserialize what I have previously stored on disk, and then continue to append to the serialization stream (which appends to the file from then on), making my serialization more or less unbounded. c) Is there currently an unbounded serialization stream? I mean, obviously the XML stream will not be 'complete' until you close the serialization stream and it can append any close tags it needs to, however if I wanted to continually write to a stream throughout the time my program is running, and if it crashes, be able to use that to get back to the state I was in, is it possible? I realize that in some respects this is kind of hammering a square peg into a round hole, since serialization seems to have been designed for 'one-short rights', but serialization and replication type functionality is very similar in nature. -- PreZ :) Death is life's way of telling you you've been fired. -- R. Geis

3 8

[1.34] Branch for release
by Thomas Witt 10 Apr '06

10 Apr '06

Hi, unless there are major issues I'd like to branch for release by the end of this week. Please let me know of any outstanding issues that should be resolved prior to branching. Thomas -- Thomas Witt witt(a)acm.org

6 6

Re: [boost] MultiArray warning under /Za
by Sohail Somani 10 Apr '06

10 Apr '06

Ronald, Thanks for changing it. Just to clarify, this is why its happening: typedef int T; int f(int T); <-- using T as a parameter when its previously declared as a type is a no-no under strict conformance(?) I hope that helps. > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Ronald Garcia > Sent: Monday, April 10, 2006 11:16 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] MultiArray warning under /Za > > Hi Sohail, > > Thanks for the information. I have checked in your suggested > patch. > Let me know if that gives you any trouble. > > Cheers, > ron > > On Apr 10, 2006, at 1:41 PM, Sohail Somani wrote: > > > It would have been VC++ 7.1 with boost 1.33.1 > > > >> -----Original Message----- > >> From: boost-bounces(a)lists.boost.org > >> [mailto:boost-bounces@lists.boost.org] On Behalf Of Ronald Garcia > >> Sent: Monday, April 10, 2006 9:29 AM > >> To: boost(a)lists.boost.org > >> Subject: Re: [boost] MultiArray warning under /Za > >> > >> Hi Sohail, > >> > >> Hmm, this warning sounds strange to me. I'm not absolutely > >> sure, but > >> it looks like an incorrect warning on the part of your > >> compiler. What > >> version of Visual C++ are you using? > >> > >> cheers, > >> ron > >> > >> > >> On Apr 5, 2006, at 2:41 PM, Sohail Somani wrote: > >> > >>> Boost 1.33.1 > >>> > >>> In multi_array.hpp: > >>> > >>> struct populate_index_ranges { > >>> multi_array_types::index_range > >>> operator()(multi_array_types::index base, > >>> multi_array_types::size_type extent) { > >>> return multi_array_types::index_range(base,base+extent); > >>> > >>> The parameter name extent seems to be typedef'ed previously. This > >>> results in: > >>> > >>> external\boost\include\boost\multi_array.hpp(46) : warning C4224: > >>> nonstandard extension used : formal parameter 'extent' was > >> previously > >>> defined as a type > >>> > >>> I've changed it in my tree to be extent_. > >>> > >>> Sohail > >>> _______________________________________________ > >>> Unsubscribe & other changes: http://lists.boost.org/mailman/ > >>> listinfo.cgi/boost > >> > >> _______________________________________________ > >> Unsubscribe & other changes: > >> http://lists.boost.org/mailman/listinfo.cgi/boost > >> > > _______________________________________________ > > Unsubscribe & other changes: http://lists.boost.org/mailman/ > > listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

1 0

Re: [boost] MultiArray warning under /Za
by Sohail Somani 10 Apr '06

10 Apr '06

It would have been VC++ 7.1 with boost 1.33.1 > -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org] On Behalf Of Ronald Garcia > Sent: Monday, April 10, 2006 9:29 AM > To: boost(a)lists.boost.org > Subject: Re: [boost] MultiArray warning under /Za > > Hi Sohail, > > Hmm, this warning sounds strange to me. I'm not absolutely > sure, but > it looks like an incorrect warning on the part of your > compiler. What > version of Visual C++ are you using? > > cheers, > ron > > > On Apr 5, 2006, at 2:41 PM, Sohail Somani wrote: > > > Boost 1.33.1 > > > > In multi_array.hpp: > > > > struct populate_index_ranges { > > multi_array_types::index_range > > operator()(multi_array_types::index base, > > multi_array_types::size_type extent) { > > return multi_array_types::index_range(base,base+extent); > > > > The parameter name extent seems to be typedef'ed previously. This > > results in: > > > > external\boost\include\boost\multi_array.hpp(46) : warning C4224: > > nonstandard extension used : formal parameter 'extent' was > previously > > defined as a type > > > > I've changed it in my tree to be extent_. > > > > Sohail > > _______________________________________________ > > Unsubscribe & other changes: http://lists.boost.org/mailman/ > > listinfo.cgi/boost > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

2 1

Re: [boost] [thread] monotonic xtime
by Matt Doyle 10 Apr '06

10 Apr '06

> -----Original Message----- > From: boost-bounces(a)lists.boost.org > [mailto:boost-bounces@lists.boost.org]On Behalf Of Ulrich Eckhardt snip> > On a related note, why doesn't the threading lib offer any > means to yield for > a certain time? In more than nine out of ten cases, this is > the way I do > things, waiting for a certain point in time - like > Boost.Thread does - is > rather the exception than the rule. I'd like to second that request, needing to use the win32 Sleep just kills the portability. My workaround for yielding is - #if defined _MSC_VER || WIN32 # include <windows.h> // for Sleep # define MILLI_SECOND_SLEEP(value) (Sleep(value)) #else # include <unistd.h> // for usleep # define MILLI_SECOND_SLEEP(value) (usleep(value * 1000)) #endif but that's just a hack, it really should be in the library. Matt Scanned by McAfee GroupShield {X3BTB534}

2 1

[FYI] RCF 0.2
by Jarl Lindrud 10 Apr '06

10 Apr '06

Hi all, I just thought I would announce that I've released v. 0.2 of RCF, a portable C++ IPC framework. It makes extensive use of boost, including Boost.Threads, Boost. Serialization, and the recently accepted asio library, so maybe people on this list will find it of interest :) http://www.codeproject.com/threads/Rcf_Ipc_For_Cpp.asp /Jarl.

7 14

[review assessment] Property tree library
by Thorsten Ottosen 10 Apr '06

10 Apr '06

Dear all, I have studied Marcin Kalicinski's Property tree library and its documentation. (For those who are interested, you may look at the library in the boost sandbox under the property_tree folders.) For a few weeks, Marcin has enhanced and simplified the interface. I now find the library fit for a review. Rewiew Wizzards, please arrange for a slot in the review queue. best regards Thorsten

1 0

boost::noninheritable class (was Re: Sealed C++ class)
by Vladislav Lazarenko 10 Apr '06

10 Apr '06

Hello, dear community. I have uploaded the code to the vault - "Generic Programming/noninheritable.zip" (http://boost-consulting.com/vault/index.php?action=downloadfile&filename=no…) The library, some documentation, examples and MSVC project files are present. It would be great if you will include this small library to official boost distribution. If no, let interested people download and use it anyway. Unfortunately, I can test it only with MSVC 7.1 now. So any help is welcome. Please review. Thank you very much for time taken to read this message and probably the code. Regards, Vladislav Lazarenko.

1 0

MultiArray warning under /Za
by Sohail Somani 10 Apr '06

10 Apr '06

Boost 1.33.1 In multi_array.hpp: struct populate_index_ranges { multi_array_types::index_range operator()(multi_array_types::index base, multi_array_types::size_type extent) { return multi_array_types::index_range(base,base+extent); The parameter name extent seems to be typedef'ed previously. This results in: external\boost\include\boost\multi_array.hpp(46) : warning C4224: nonstandard extension used : formal parameter 'extent' was previously defined as a type I've changed it in my tree to be extent_. Sohail

2 1