Jeremy Maitin-Shepard wrote:
> The thread library as of boost 1.30 does provide a struct xtime, which
> is similar to timeval, except that xtime represents a time, while
> timeval represents a time duration. The documentation for the thread
> library suggests, however, that xtime is intended a
Jeff Garland wrote:
> I think that it is broader than sockets. The thread library, for
> example, uses something that basically amounts to timeval in
> some cases. Finally, if someone wanted to use a different socket
> library (especially since boost.socket isn't in boost) why make
> them rewrite
Jeff Garland wrote:
I think that it is broader than sockets. The thread library, for
example, uses something that basically amounts to timeval in
some cases. Finally, if someone wanted to use a different socket
library (especially since boost.socket isn't in boost) why make
them rewrite this cod
> On Mon, Jun 23, 2003 at 06:53:28AM -0700, Jeff Garland wrote:
> > [snip]
> > Ok will do. I'll add some protections or rounding for when durations
> > support higher than microsecond resolution. I'll let you know when
> > this gets added.
>
> It seems that since 1) timeval is non-(C++) standar
On Mon, Jun 23, 2003 at 06:53:28AM -0700, Jeff Garland wrote:
> [snip]
> Ok will do. I'll add some protections or rounding for when durations
> support higher than microsecond resolution. I'll let you know when
> this gets added.
It seems that since 1) timeval is non-(C++) standard, and 2) it is
Jeff Garland wrote:
Ok will do. I'll add some protections or rounding for when durations
support higher than microsecond resolution. I'll let you know when
this gets added.
Thanks a lot !
Stefan
___
Unsubscribe & other changes: http://lists.boost.org
S. Seefeld wrote
> I'd suggest these two converters to be added:
>
> timeval to_timeval(const ptime &t)
>...
>
> timeval to_timeval(const time_duration &d)
>...
>
> the latter is especially useful as select() operates with durations,
> so there is no need to convert between 1970-01-01 relative
Jeff Garland wrote:
I'd like to replace my code by boost::date_time, but conversion
from boost::date_time to timeval doesn't seem to be supported.
You are right, but this would make a nice addition.
I'd suggest these two converters to be added:
timeval to_timeval(const ptime &t)
{
ptime timet
> I note that boost::posix_time supports on certain platforms
> the generation of a ptime from a timeval (using gettimeofday()).
>
> I have a time class in my own project which can be cast from/to
> timeval, so I can use it in conjunction with calls to 'select()',
> which expects a timeval pointe
On Thu, 19 Jun 2003 17:15:11 -0400, Stefan Seefeld wrote
> little precision:
>
> the posix_time::time_duration type seems to come close to
> what I want. However, the documentation isn't very clear on
> what 'fractional_seconds()' actually stands for.
fractional_seconds is a count. It is relativ
little precision:
the posix_time::time_duration type seems to come close to
what I want. However, the documentation isn't very clear on
what 'fractional_seconds()' actually stands for.
Does the 'unit()' function return 1 unit expressed in nanoseconds ?
If so, why is it returning a time_duration an
11 matches
Mail list logo
