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: 103376,52fd60a337c05842 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-06-15 04:48:54 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!newsfeed.belnet.be!news.belnet.be!newsfeed.vmunix.org!fu-berlin.de!uni-berlin.de!pd955e9ab.dip.t-dialin.NET!not-for-mail From: Immanuel Scholz Newsgroups: comp.lang.ada Subject: Re: ada paper critic Date: Sat, 15 Jun 2002 13:49:55 +0200 Message-ID: References: NNTP-Posting-Host: pd955e9ab.dip.t-dialin.net (217.85.233.171) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Trace: fu-berlin.de 1024141733 6894967 217.85.233.171 (16 [100557]) User-Agent: KNode/0.6.1 Xref: archiver1.google.com comp.lang.ada:26018 Date: 2002-06-15T13:49:55+02:00 List-Id: Dale Stanbrough wrote: > You could utilise the streams feature to convert it to/from > in a standardised way, but to me that seems a lot of work > compared to the Java equivalent. Yes, and also this would drop your coding style to a level of "unsage typecasts". (Theoretically you can cover _all_ variable types by just use a unique string-representation and parse them at need ;-) I think the idea of exceptions in Ada are more restrictive than in other languages as Java. In Java it is a more or fewer "normal" exit state of any function to raise an exception on error conditions (e.g. File not found, Disk full, invalid xml-document etc.) In Ada, I guess, exceptions have only to be thrown in real critical situations, where something unpredictable have been done, as violating the contract with a function. In this case, exception is more an assert than an java.lang.Exception. Am I right? What is the real practise use of exceptions in Ada? Immanuel Scholz