Related articles |
---|
COBOL Parsers mrickan@home.com (Mark Rickan) (2000-04-15) |
Re: COBOL Parsers waratah@zip.com.au (Ken Foskey) (2000-04-16) |
Re: COBOL Parsers vadik@siber.com (Vadim Maslov) (2000-04-16) |
Re: COBOL Parsers eil@kingston.net (John H. Lindsay) (2000-04-17) |
Re: COBOL Parsers tej@melbpc.org.au (Tim Josling) (2000-04-20) |
Re: COBOL Parsers thaneH@softwaresimple.com (2000-04-25) |
From: | thaneH@softwaresimple.com (Thane Hubbell) |
Newsgroups: | comp.lang.cobol,comp.compilers |
Date: | 25 Apr 2000 02:09:02 -0400 |
Organization: | Posted via Supernews, http://www.supernews.com |
References: | 00-04-120 00-04-129 00-04-145 |
Keywords: | parse, Cobol |
On 20 Apr 2000 01:36:57 -0400, Tim Josling <tej@melbpc.org.au> wrote:
>Similar problems exist in other parts of the language. It is not
>actually rocket science but it does make it hard to provide good error
>messages.
Speaking of error messages, I got an interesting one from the Fujitsu
v5 compiler the other day. Had me laughing.
What it meant to say was "Required file is missing". But what it said
(and remember these messages were translated directly from Japanese
into english):
A file that does not exist was found.
Return to the
comp.compilers page.
Search the
comp.compilers archives again.