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-Thread: 103376,8da181ade72859cf X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.glorb.com!wn14feed!worldnet.att.net!attbi_s51.POSTED!53ab2750!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: timeouts References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 24.6.132.82 X-Complaints-To: abuse@comcast.net X-Trace: attbi_s51 1093570310 24.6.132.82 (Fri, 27 Aug 2004 01:31:50 GMT) NNTP-Posting-Date: Fri, 27 Aug 2004 01:31:50 GMT Organization: Comcast Online Date: Fri, 27 Aug 2004 01:31:50 GMT Xref: g2news1.google.com comp.lang.ada:3068 Date: 2004-08-27T01:31:50+00:00 List-Id: >In my case the solutions I have seen don't seem feasible: Comparing my version of s-osprim.adb and the one from ACT, I note the addition of one (initialization) line: Comparing files S-OSPRIM.ADB and L:S-OSPRIM.ADB ***** S-OSPRIM.ADB Long_Long_Float (Sec_Unit)); Base_Monotonic_Clock := Base_Clock; end Get_Base_Time; ***** L:S-OSPRIM.ADB Long_Long_Float (Sec_Unit)); end Get_Base_Time; ***** ***** S-OSPRIM.ADB Of course you'll then need to compile s-osprim.adb with the compiler option that lets to recompile system components (which I don't recall off the top of my head) and you'll have to recompile the things that depend on s-osprim.adb (IIRC that's more than you would expect). Is the current GCC Gnat more robust than 3.15p, or is it still beta? ie, should we (Windows) 3.15p users switch, or continue waiting?