caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Milan Stanojević" <milanst@gmail.com>
To: "Markus W. Weißmann" <markus.weissmann@in.tum.de>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] POSIX time implementation
Date: Sat, 5 Sep 2015 20:04:28 -0400	[thread overview]
Message-ID: <CAKR7PS9wmSyJua4B1bNdbCNNd6Un9rgxmnTCJiODGkeJTpASXQ@mail.gmail.com> (raw)
In-Reply-To: <2CA44FB5-DDEF-48A6-8567-99DCE4A0BA66@in.tum.de>

[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]

Jane Street's Core_kernel has Time_ns module. Time is represented as an
int, number of nanoseconds since unix epoch. Time_ns.now uses
clock_gettime(CLOCK_REALTIME)
There are also usual functions for operating on time and time spans.
Not sure if Core_kernel is too big for your project.
Hi,

I was searching for an existing library implementing a clock_gettime(2)
function that would deliver a ‘struct timespec’ [1] with the current time.
I want it for my POSIX message queue implementation [2] for the timed
functions that require an absolute ‘struct timespec’ for their timeout.
So what a user of mqueue requires is a 1.) function to get the current time
as ‘struct timespec’ and 2.) to add seconds/nanoseconds to such a value to
create a timeout.

The existing solutions I found:
* The Unix library [3] implements ‘struct timeval’ as float (only
microseconds, imho the float conversion is a bit of a hack — a clever one
though)
* Netsys.clock_gettime from ocamlnet [4] implements ’struct timespec’ but
has it as float/int for seconds/nanoseconds (whats with the float? All
systems I found use either in32 or int64 for time_t)
* Mtime [5] implements clock_gettime(2) but seems to only offers relative
values
* Ptime [6] appears to be the uber-POSIX time implementation but lacks
clock_gettime (and probably always will)

I’d like my library to be a good OCaml citizen and _not_ implement my own
special purpose timing functions (which are incompatible to everyone
else’s).
Ptime looks like the ultimate solution for the datatype; ocamlnet gets the
closest to my requirements — while being a gigantic library most of which
has nothing to do with the domain of mqueue.

I’m a bit stuck on this one and would like to get some advice — and/or
corrections if I misinterpreted one of the above solutions.

regards
-Markus

[1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/time.h.html
[2] http://mqueue.forge.ocamlcore.org/
[3] http://caml.inria.fr/pub/docs/manual-ocaml/libref/Unix.html
[4]
http://projects.camlcity.org/projects/dl/ocamlnet-4.0.4/doc/html-main/Netsys_posix.html
[5] http://erratique.ch/software/mtime
[6] http://erratique.ch/software/ptime

--
Markus Weißmann, M.Sc.
Technische Universität München
Institut für Informatik
Boltzmannstr. 3
D-85748 Garching
Germany
http://wwwknoll.in.tum.de/


--
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

[-- Attachment #2: Type: text/html, Size: 3881 bytes --]

  parent reply	other threads:[~2015-09-06  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05 11:52 "Markus W. Weißmann"
2015-09-05 16:59 ` Gerd Stolpmann
2015-09-06  0:04 ` Milan Stanojević [this message]
2015-09-08  9:02 ` Markus Weißmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKR7PS9wmSyJua4B1bNdbCNNd6Un9rgxmnTCJiODGkeJTpASXQ@mail.gmail.com \
    --to=milanst@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=markus.weissmann@in.tum.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).