coq-club AT inria.fr
Subject: The Coq mailing list
List archive
- From: Pierre-Marie Pédrot <pierre-marie.pedrot AT inria.fr>
- To: coq-club AT inria.fr
- Subject: Re: [Coq-Club] Definitions for Parsing Compatibility
- Date: Thu, 18 Feb 2016 11:17:38 +0100
On 17/02/2016 22:51, scott constable wrote:
> What exactly is the purpose of reintroducing existing tactics as
> identical notations?
AFAIK, that's purely a parsing issue.
Since Coq 8.5, some tactics defined in ML are registered as true Ltac as
they do not require parsing rules. Typically, tactics whose grammar is
of the form
"ident" constr₁ ... constrₙ
for any n. Alas, this clashes with some other notations that are indeed
changing the parsing rules. For instance, in the list you mentionned,
"constructor" has a variant "constructor" integer(i). This leads to
various issues that prevent parsing "constructor" alone.
PMP
Attachment:
signature.asc
Description: OpenPGP digital signature
- [Coq-Club] Definitions for Parsing Compatibility, scott constable, 02/17/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, Pierre Courtieu, 02/18/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, Pierre-Marie Pédrot, 02/18/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, scott constable, 02/18/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, Pierre Courtieu, 02/20/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, scott constable, 02/20/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, Pierre Courtieu, 02/20/2016
- Re: [Coq-Club] Definitions for Parsing Compatibility, scott constable, 02/18/2016
Archive powered by MHonArc 2.6.18.