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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2b151131f90050ab X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-29 19:11:58 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator-SanJose!in.nntp.be!news-in-sanjose!newshub2.rdc1.sfba.home.com!news.home.com!news1.rdc1.sfba.home.com.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Ada, calendar, and daylight savings References: <3BDE0B8D.6040409@acm.org> X-Newsreader: Tom's custom newsreader Message-ID: <1UoD7.89699$gT6.46253885@news1.rdc1.sfba.home.com> Date: Tue, 30 Oct 2001 03:11:57 GMT NNTP-Posting-Host: 24.7.82.199 X-Complaints-To: abuse@home.net X-Trace: news1.rdc1.sfba.home.com 1004411517 24.7.82.199 (Mon, 29 Oct 2001 19:11:57 PST) NNTP-Posting-Date: Mon, 29 Oct 2001 19:11:57 PST Organization: Excite@Home - The Leader in Broadband http://home.com/faster Xref: archiver1.google.com comp.lang.ada:15390 Date: 2001-10-30T03:11:57+00:00 List-Id: > > You want that timezone to be UTC. Why not just replace the > > package body Ada.Calendar that your compiler supplies, with a > > different one that returns UTC for Clock? > But what if I want a portable package that does this, one that works > with multiple compilers? Surely portability should be one of Ada's How to get what you want: 1) Wait for Ada 0Y 2) Design a commonly accepted approach, then get all the relevant compiler vendors to implement for each platform. 3) Design your own portable package specs, and implement on each platform you need. 4) Use the existing Ada.Calendar for a spec, and implement a UTC body for each compiler/platform your need. You do of course have synchronized clocks in all your distributed heterogenous systems. Or your new package gets its clock from a central source, regardless of where the program is running, and you don't allow anyone to use (unsynchronized) Ada.Calendar Other solutions?