[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Recovery (was Re: gnubol: How do we parse this language,anyway?)

To: gnu-cobol@lusars.net
Subject: Re: Recovery (was Re: gnubol: How do we parse this language,anyway?)
From: Tim Josling <TIMJOSLING@prodigy.net>
Date: Fri, 10 Dec 1999 15:19:05 +1000
Delivered-To: gnu-cobol-outgoing@wallace.lusars.net
References: <0.535526c3.2580f8b3@aol.com> <3.0.3.32.19991209160223.0069ef68@tiac.net>
Reply-To: gnu-cobol@lusars.net
Sender: owner-gnu-cobol@wallace.lusars.net

Yep, I'll be recovering like that, but I can't do anything better. In other areas,
I can do better,
Tim Josling

"J & C Migrations, Pty." wrote:

> Recovery is usually best by skipping to the next verb (begining of
> sentence) on a bad error, or to the next period (EOS) if it is a very bad
> error.


--
This message was sent through the gnu-cobol mailing list.  To remove yourself
from this mailing list, send a message to majordomo@lusars.net with the
words "unsubscribe gnu-cobol" in the message body.  For more information on
the GNU COBOL project, send mail to gnu-cobol-owner@lusars.net.

References:
- Re: gnubol: How do we parse this language, anyway?
  - From: RKRayhawk@aol.com
- Recovery (was Re: gnubol: How do we parse this language, anyway?)
  - From: "J & C Migrations, Pty." <migrate@tiac.net>

Prev by Date: Re: gnubol: How do we parse this language, anyway?
Next by Date: FW: gnubol: How do we parse this language, anyway?
Prev by thread: Recovery (was Re: gnubol: How do we parse this language, anyway?)
Next by thread: Re: gnubol: How do we parse this language, anyway?
Index(es):
- Date
- Thread