From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: *** X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b1850e397df49d95 X-Google-Attributes: gid103376,public From: "Jerry van Dijk" Subject: Re: How to convert an Fixed_Point to to an Integer ? Date: 1996/12/27 Message-ID: <01bbf3d9$b7b0f120$f22d5c8b@jerryware>#1/1 X-Deja-AN: 206179102 references: <01bbf058$cbdbf980$LocalHost@jerryware> <1996Dec23.072835.1@eisner> <01bbf179$0c4361e0$9b2d5c8b@jerryware> <01bbf24c$a8db4800$b72d5c8b@jerryware> <32C2A408.53B8@watson.ibm.com> organization: *JerryWare HQ*, Haarlem, Holland newsgroups: comp.lang.ada Date: 1996-12-27T00:00:00+00:00 List-Id: Norman, Norman H. Cohen wrote in article <32C2A408.53B8@watson.ibm.com>... > slight complication, and this approach does not account for leap > seconds, but I'm not sure how Unix systems deal with leap seconds > either Good question. My normal Unix bible (Stevens, 'Advanced programming in the Unix Enviroment, AW, 9th printing, july 1995) keeps almost silent about it. But on page 155 Stevens says: "struct tm { /* a broken down time */ int tm_sec; /* Seconds after the minute: [0, 61] */ ... The reason that seconds can be greater than 59 is to allow for leap seconds." And as the DJGPP info documents this fields as [0, 60] I am reasonable convinced that leaps are taken care of in both systems. > package Epoch is > > > -- Note: This package works from the beginning of 1970 until the end of > -- 2099, after which the package Ada.Calendar is no longer usable. > -- During this period, a year y is a leap year if and only if y > mod 4 = 0. Gee, and I only asked about it... Thanks Norman! Jerry,