caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Samuel Lelievre <samuel.lelievre@free.fr>
To: Caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] date - waiting for 64-bit
Date: Thu, 9 Sep 2004 15:20:38 +0200	[thread overview]
Message-ID: <a06110457bd66054bb01c@[162.38.126.189]> (raw)
In-Reply-To: <20040909122103.GA27255@bourg.inria.fr>

Basile Starynkevitch wrote:
>I suggest to switch to Ocaml (even on a 32 bits machine)
>
>% ocaml
>         Objective Caml version 3.08.0
>
># #load "unix.cma";;
># Unix.time ();;
>- : float = 1094732223.
># Unix.gmtime (Unix.time ());;
>- : Unix.tm =
>{Unix.tm_sec = 16; Unix.tm_min = 17; Unix.tm_hour = 12; Unix.tm_mday = 9;
>  Unix.tm_mon = 8; Unix.tm_year = 104; Unix.tm_wday = 4; Unix.tm_yday = 252;
>  Unix.tm_isdst = false}
>#
>
>I am not sure that staying in Caml Light is a sensible thing to do,
>especially for code that you are working on. Maybe taking the
>necessary time to port your code from Caml-Light (which is not active
>anymore) to Ocaml (which is actively developped and has a bigger
>community) is really worth the effort.

Do you mean that the integers of type int are not mod 2^31 in Ocaml?

That's certainly an argument to make me make my mind to switch,
which I was postponing forever, having failed to translate my
simple programs to Ocaml (I have to confess I did not try hard).

I learnt how to use the "num" library in order to deal with larger
integers than 2^30, but if Ocaml makes it simpler...

I was sticking to the advice on
http://caml.inria.fr/ocaml/bigpicture.html

   Should I switch from Caml Light to Objective Caml?

   Caml Light is still maintained, though no longer actively
   developed.  We make bug-fix releases from time to time and
   still provide support for it.  It provides a more stable
   programming environment than Objective Caml, which is still
   evolving, though at a slower pace than immediately after its
   introduction.

   If you're perfectly happy with Caml Light, value reliability
   more than performance, don't need the new module system, don't
   need the new object stuff, then stay with Caml Light. If you
   need objects, powerful modules, the native-code compiler, or
   just like being on the cutting edge, go for Objective Caml.


Samuel Lelievre

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-09-09 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 11:55 [Caml-list] date - waiting for 64-bit (was: Gripes with array) Samuel Lelievre
2004-09-09 12:21 ` Basile Starynkevitch [local]
2004-09-09 13:20   ` Samuel Lelievre [this message]
2004-09-09 13:44     ` [Caml-list] date - waiting for 64-bit Basile Starynkevitch [local]
2004-09-09 14:03       ` Marcin 'Qrczak' Kowalczyk
2004-09-09 13:49     ` Marcin 'Qrczak' Kowalczyk
2004-09-09 16:12 ` [Caml-list] date - waiting for 64-bit (was: Gripes with array) james woodyatt

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='a06110457bd66054bb01c@[162.38.126.189]' \
    --to=samuel.lelievre@free.fr \
    --cc=caml-list@inria.fr \
    /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).