Path: csiph.com!xmission!news.snarked.org!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end
From: David Lovemore <davidlovemore@gmail.com>
Newsgroups: comp.compilers
Subject: Supporting multiple input syntaxes
Date: Sat, 15 Aug 2020 06:42:29 -0700 (PDT)
Organization: Compilers Central
Lines: 4
Sender: news@iecc.com
Approved: comp.compilers@iecc.com
Message-ID: <20-08-009@comp.compilers>
References: <20-08-002@comp.compilers>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="860"; mail-complaints-to="abuse@iecc.com"
Keywords: parse
Posted-Date: 15 Aug 2020 10:46:44 EDT
X-submission-address: compilers@iecc.com
X-moderator-address: compilers-request@iecc.com
X-FAQ-and-archives: http://compilers.iecc.com
In-Reply-To: <20-08-002@comp.compilers>
Xref: csiph.com comp.compilers:2561

It may be useful to consider what you would like to happen if you encounter a
syntax that is ambiguous or works differently or is for another expected
syntax from what you are parsing: produce a warning, error or handle quietly,
or fall over, or don’t care.