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,820de86ed0dafb8a X-Google-Attributes: gid103376,public From: Brian Rogoff Subject: Re: Help Me Please :) Date: 2000/03/20 Message-ID: #1/1 X-Deja-AN: 600020416 References: <89rlvr$gn9$1@nntp3.atl.mindspring.net> Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: nntp1.ba.best.com 953575073 210 bpr@206.184.139.136 MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-03-20T00:00:00+00:00 List-Id: On Sun, 19 Mar 2000, Robert A Duff wrote: > "James S. Rogers" writes: > > > Have you ever used exceptions in C++? > > No. The last time I used C++ (some years ago), most compilers did not > support exceptions. The closest I could get was reading about them in > Stroustrup's book. But I have used exceptions in other languages that > define exceptions as first-class objects. > > >...Very few people do. > > The problem arises from the fact that exceptions are first class objects. > > I don't understand this problem. Perhaps you could give an example? Is > the problem you're talking about C++-specific, or are you claiming it's > a fundamental problem with the idea of exceptions-as-objects? I agree with Bob Duff here, in that I don't understand. When I was hacking Java, my complaint about the exception mechanism wasn't that you could throw objects, it was that you had to declare or catch all exceptions, which causes lots of people to subclass from RuntimeException to avoid this. But that's not the issue at hand. I think exception types would be a good thing, but its way too late to fix that now, and it was probably too late for Ada 95. A future Ada-inspired language could fix this. -- Brian