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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,50ad4ada98045ba X-Google-Attributes: gid103376,public From: mgk25@cl.cam.ac.uk (Markus Kuhn) Subject: Re: locating exceptions (Ada vs. Java) Date: 1999/03/20 Message-ID: <7cvu1s$14g$2@pegasus.csx.cam.ac.uk>#1/1 X-Deja-AN: 456861478 References: <119fb4e248%hubersn@lcs.wn.bawue.de> <36efef1c.3265725@news.pacbell.net> <7cp9cp$743$1@nnrp1.dejanews.com> <36F0A77F.B0151962@rocketmail.com> <7crpn2$kt6@drn.newsguy.com> Organization: U of Cambridge Computer Lab, UK Newsgroups: comp.lang.ada Date: 1999-03-20T00:00:00+00:00 List-Id: In article <7crpn2$kt6@drn.newsguy.com>, bill writes: |> Java does all that out of the box. I found Ada exception tracing to be weak |> compared to Java more powerfull exceptions. In Java, an exception is an object, |> that contains very usefull info that one can use. What does Java do in the case of out-of-memory exceptions in small embedded systems (e.g., Java smartcard with 256 bytes RAM), where there might not be space free for allocating an exception object? Ada's exception mechanism sounds to me less comfortable, but more foolproof here, as it does not rely on an operational heap. Also remember that Ada was designed to allow using a heap-free subset of the language for high-assurance applications (you do not want to rely on malloc() in pacemakers and chemical process control software). Markus -- Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK Email: mkuhn at acm.org, WWW: