From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA29249 for caml-redistribution; Tue, 7 Sep 1999 11:46:41 +0200 (MET DST) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA14404 for ; Mon, 6 Sep 1999 19:52:29 +0200 (MET DST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.8.7/8.8.7) with ESMTP id TAA01815; Mon, 6 Sep 1999 19:52:22 +0200 (MET DST) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id TAA11180; Mon, 6 Sep 1999 19:52:21 +0200 (MET DST) Message-ID: <19990906195221.19299@pauillac.inria.fr> Date: Mon, 6 Sep 1999 19:52:21 +0200 From: Xavier Leroy To: Friedman Roy , caml-list@inria.fr Subject: Re: Y2K related changes References: <19990831211612.50360@pauillac.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: ; from Friedman Roy on Wed, Sep 01, 1999 at 06:23:22PM +0300 Sender: weis > Were there any Y2K related changes in Ocaml from version 1.05 to 2.02? No year 2000 changes. As far as we know, all versions of OCaml are Y2K-safe. However, OCaml 1 has a year 2004 problem in the Unix library: the type "int" was used to represent a number of seconds since the Unix epoch, and since Caml integers are signed, 31 bit (on 32-bit platforms), this causes a roll-over in Jan 2004. To work around this problem, OCaml 2 uses the type "float" to represent Unix time. This ensures correct time values till the year 570843811, and progressive degradation of the accuracy of time values afterwards :-) - Xavier Leroy