Skip to Content.
Sympa Menu

coq-club - Re: [Coq-Club] Non strictly positive occurrence of "execute"

coq-club AT inria.fr

Subject: The Coq mailing list

List archive

Re: [Coq-Club] Non strictly positive occurrence of "execute"


Chronological Thread 
  • From: Adam Chlipala <adamc AT csail.mit.edu>
  • To: Liang Dou <ldou.ecnu AT gmail.com>
  • Cc: coq-club AT inria.fr
  • Subject: Re: [Coq-Club] Non strictly positive occurrence of "execute"
  • Date: Tue, 18 Dec 2012 07:34:34 -0500

On 12/17/2012 10:12 PM, Liang Dou wrote:
Hi , all
We have an inductive definition "execute" and we get the error for coq:

Non strictly positive occurrence of "execute" in
"forall s : state,
state ->
forall (l l' : state) (a : event),
(forall s'0 : state, ~ execute s (a :: nil) s'0) ->
prefix s l = true -> execute l (a :: nil) l'".

=======================================
Definition event:=string.
Definition state:=string.
Definition action:=list event.

Inductive execute: state -> action -> state ->Prop :=
|OR1: forall (s s' l l' : state) ( a : event),
(forall s', ~ (execute s (a::nil) s')) ->
prefix s l = true ->
execute l (a::nil) l' .


could someone tell ue how to fix it?

I assume it's clear that your definition is not even positive, let alone strictly positive. There is a good chance that admitting your definition would create a logical inconsistency, though I haven't verified it for sure.

For more information on why Coq needs to enforce this restriction, see Section 3.6 of CPDT <http://adam.chlipala.net/cpdt/>.

As Cedric wrote, it is not obvious that there is a trivial restatement of your definition that will be legal. One has to know more context for such things. One promising albeit inconvenient option might be to define a [notExecute] mutual inductive that covers all the ways that [execute] might fail.



Archive powered by MHonArc 2.6.18.

Top of Page