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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,88c174f3c455ecdc X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-07 13:37:35 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!headwall.stanford.edu!unlnews.unl.edu!newsfeed.ksu.edu!nntp.ksu.edu!news.okstate.edu!not-for-mail From: David Starner Newsgroups: comp.lang.ada Subject: Re: Thoughts on the ADaOS user program interface Date: 7 Sep 2001 19:35:29 GMT Organization: Oklahoma State University Message-ID: <9nb7i1$7pu1@news.cis.okstate.edu> References: <9n8eks$qsp$1@shell.monmouth.com> <3B98FA64.4080907@home.com> Reply-To: dstarner98@aasaa.ofe.org NNTP-Posting-Host: x8b4e5129.dhcp.okstate.edu User-Agent: slrn/0.9.7.2 (Linux) Xref: archiver1.google.com comp.lang.ada:12915 Date: 2001-09-07T19:35:29+00:00 List-Id: On Fri, 07 Sep 2001 16:48:37 GMT, Warren W. Gay VE3WWG wrote: > indeed care, and often must take appropriate action. One issue that > comes up in UNIX/BSD is the EINTR/EAGAIN error, that occurs when > a system call is interrupted due to the handling of a signal. Now > this could be handled at the O/S level differently in AdaOS, but it > may not always be simple (i.e. do you proceed with the system call > that is in progress, save its interrupted state, or back out the > system call as UNIX often does - returining EINTR/EAGAIN?) I thought that was fixed with BSD 4.2, over a decade ago. -- David Starner - dstarner98@aasaa.ofe.org Pointless website: http://dvdeug.dhis.org "I don't care if Bill personally has my name and reads my email and laughs at me. In fact, I'd be rather honored." - Joseph_Greg