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-Thread: 103376,699cc914522aa7c4
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 16 Jan 2007 16:54:55 -0600
From: "Randy Brukardt" <randy@rrsoftware.com>
Newsgroups: comp.lang.ada
References: <eog0g5$2bn$1@cernne03.cern.ch> <u7ivnp09z.fsf@stephe-leake.org>
 <eoinoh$855$1@cernne03.cern.ch> <Ij8rh.226765$aJ.8694@attbi_s21>
Subject: Re: Structured exception information
Date: Tue, 16 Jan 2007 16:55:51 -0600
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Message-ID: <VfGdnSR8bp4iyjDYnZ2dnUVZ_qmpnZ2d@megapath.net>
NNTP-Posting-Host: 64.32.209.38
X-Trace: 
 sv3-n4gdKOqY4PKF/oJmPuD+f230+daETSqk9LxKJkyGAWl/BKB3t+otrCVJargXSo7CKhuX5apNmGummNV!hFlY7QTPwSXSp4jI2EbY4iQwTjdzeJkY8KkRbzaO2qtUixi7SgixPNF0p1A2jj6uvWUAmSC1RyzX!Nsi4tg1lP+T/Gg==
X-Complaints-To: abuse@megapath.net
X-DMCA-Complaints-To: abuse@megapath.net
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.3.32
Xref: g2news2.google.com comp.lang.ada:8206
Date: 2007-01-16T16:55:51-06:00
List-Id: <comp.lang.ada>

"Jeffrey Carter" <spam.jrcarter.not@spam.acm.not.org> wrote in message
news:Ij8rh.226765$aJ.8694@attbi_s21...
> Maciej Sobczak wrote:
> >
> > Another example - imagine that your compiler just prints
> > "COMPILER_ERROR" instead of everything that it actually prints.
> > That wouldn't be very funny!
>
> Since Compiler_Error would be an error with the compiler, not with the
> source code it was compiling, this would apparently be a compiler that
> couldn't compile anything. Now a compiler that just said "Compilation
> error" for any errors in the source would be irritating. Might be a good
> learning tool, though.

The error handling of early Ada compilers, especially for resolution errors,
was essentially this. You still see it once in a while with complex
expressions where the compiler cannot figure out what it is that you're
doing.

                           Randy.