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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,cfd23c10fd537a80 X-Google-Attributes: gid103376,public From: randhol+nospam@pvv.org (Preben Randhol) Subject: Ada Calendar oddity Date: 2000/05/10 Message-ID: #1/1 X-Deja-AN: 621555306 References: <39176D85.603D7AEC@research.canon.com.au> <39178DEA.FD2C20FA@research.canon.com.au> <8f92o1$6v$1@nnrp1.deja.com> <3918BB77.693C70D6@research.canon.com.au> <8fahfv$mgt$1@nnrp1.deja.com> X-Complaints-To: usenet@itea.ntnu.no X-Trace: kopp.stud.ntnu.no 957964666 6550 129.241.83.82 (10 May 2000 13:17:46 GMT) Organization: Norwegian university of science and technology User-Agent: slrn/0.9.6.2 (Linux) NNTP-Posting-Date: 10 May 2000 13:17:46 GMT Newsgroups: comp.lang.ada Date: 2000-05-10T13:17:46+00:00 List-Id: I was looking yesterday in the RM and found that Year in the Ada.Calendar was defined until 2099 only. I have search on deja, but I cannot find any reason for it to be defined only to 2099. Some would claim that 2099 is a long way in the future, but I think it isn't in all respects. An example: If I were to make a program for issuing drivers licenses here in Norway there would be a problem. Well not immediately but in only 18 years. The reason is that driver's licenses expires as you get 100 years old. So mine expires in 2073. If one wanted to use the Year type in Ada.Calendar for birthday and expiration date, one would get an constraint error when one issued drivers licences for these born this year. Wouldn't one? I may have missed some thing important when I speedily "read" the Ada.Calendar, but this seems a bit odd to me (the upper limit that is). -- Preben Randhol -- [randhol@pvv.org] -- "Det eneste trygge stedet i verden er inne i en fortelling." -- Athol Fugard