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,FREEMAIL_FROM, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,2d2df3e9ad18fa63 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-20 13:48:23 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!small1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!intern1.nntp.aus1.giganews.com!nntp.giganews.com!nntp.gbronline.com!news.gbronline.com.POSTED!not-for-mail NNTP-Posting-Date: Fri, 20 Jun 2003 15:48:21 -0500 Date: Fri, 20 Jun 2003 15:49:08 -0500 From: Wesley Groleau Reply-To: wesgroleau@despammed.com Organization: Ain't no organization here! User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en, es-mx, pt-br, fr-ca MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: ISO/IEC 14519 - Ada POSIX binding References: <3EF2F6B8.3030706@noplace.com> <3EF338C5.2010005@cogeco.ca> In-Reply-To: <3EF338C5.2010005@cogeco.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: NNTP-Posting-Host: 216.117.18.129 X-Trace: sv3-3Mu5knfFqHStf01BlphsGrbabc2hwzwpWngIpQMRk+8JYhVdspM19HtVSVyNeeLX1keVKlkzNGEM/w6!YHH4UBQ6HcR9NDVVRLG8LN5exOZAxmtStclrK8uRQNuHfnk4UsFzjEHFJQyFHTZ/lFBOtw6FMZfF!M/Fv9g== X-Complaints-To: abuse@gbronline.com X-DMCA-Complaints-To: abuse@gbronline.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 Xref: archiver1.google.com comp.lang.ada:39505 Date: 2003-06-20T15:49:08-05:00 List-Id: > But there _are_ problems WRT Ada. The first that comes to mind is > the whole error handling approach. POSIX likes the idea of an errno > value with errno codes. The Ada approach often uses exceptions, and > perhaps supplementary information APIs, which differ decidedly from > the POSIX interface. The POSIX binding I looked at had a single exception, POSIX_Error and then you were supposed to examine the errno variable. Proctalgia, but it's the price you pay for interfacing to such a primitive system. Rather than "roll-your-own" completely, I'd say use POSIX as a thin binding and provide a thick binding to wrap it in.