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: fdb77,5f529c91be2ac930 X-Google-Attributes: gidfdb77,public X-Google-Thread: 103376,583275b6950bf4e6 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,59ec73856b699922 X-Google-Attributes: gid1108a1,public X-Google-Thread: 11232c,59ec73856b699922 X-Google-Attributes: gid11232c,public X-Google-ArrivalTime: 2003-05-02 11:43:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!logbridge.uoregon.edu!newsfeed.stueberl.de!eusc.inter.net!cs.tu-berlin.de!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.java.advocacy,comp.object,comp.lang.ada,misc.misc Subject: Re: Using Ada for device drivers? Date: Fri, 2 May 2003 18:43:07 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <9fa75d42.0304230424.10612b1a@posting.google.com> <9fa75d42.0304240446.493ca906@posting.google.com> <3EA7E0E3.8020407@crs4.it> <9fa75d42.0304240950.45114a39@posting.google.com> <4a885870.0304291909.300765f@posting.google.com> <416273D61ACF7FEF.82C1D1AC17296926.FF0BFD4934A03813@lp.airnews.net> NNTP-Posting-Host: d2-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1051900987 3455 134.91.1.15 (2 May 2003 18:43:07 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Fri, 2 May 2003 18:43:07 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/831)) Xref: archiver1.google.com comp.lang.java.advocacy:63061 comp.object:62586 comp.lang.ada:36881 misc.misc:13913 Date: 2003-05-02T18:43:07+00:00 List-Id: In comp.lang.ada Kaz Kylheku wrote: : Ada's exception system is not useful for much more than containing : errors. Which is what is is made for? : The correct design for error handling is to unwind to an : outer dynamic context *as a the very last step*, after an analysis is : performed and the proper place to unwind to has been chosen. Correct WRT what? This computation will certainly take some time, which may be a completely incorrect choice given some desired run time behaviour. (For example, a retry a la Eiffel, without analysis, might be just quick enough.) : I'm warmly entertained, by the way, by how the string returned by : Exception_Message may be truncated to 200 characters. Ah, assembly : language and its fixed buffers. Where in assembly language is there a requirement for fixed buffers? Where in assembly language are there buffers at all, for a start? Oh these darn fixed buffers. Can't we compute on an infinite tape? Seriously, I think these interesting thoughts deliberately hide their assumptions about the prerequisites for execution of the program. Otherwise we might as well introduce dynamic programming into error handling. Which is certainly quite interesting. Georg