2014
DOI: 10.1007/978-3-319-07151-0_17
|View full text |Cite
|
Sign up to set email alerts
|

Semantics for Prolog with Cut – Revisited

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
1
1
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 10 publications
0
3
0
Order By: Relevance
“…Recently, the application of certified/mechanized approaches came into focus as well. In particular, in [19] the equivalence of a few differently defined operational semantics for pure Prolog is proven, and in [18] a denotational semantics for Prolog with cut is presented; both works provide Coq-mechanised proofs. It is interesting that the former one also advocates the use of higher-order abstract syntax.…”
Section: Related Workmentioning
confidence: 99%
“…Recently, the application of certified/mechanized approaches came into focus as well. In particular, in [19] the equivalence of a few differently defined operational semantics for pure Prolog is proven, and in [18] a denotational semantics for Prolog with cut is presented; both works provide Coq-mechanised proofs. It is interesting that the former one also advocates the use of higher-order abstract syntax.…”
Section: Related Workmentioning
confidence: 99%
“…Usually the semantics of the cut is described in terms of explicit representation of computation states, stacks of backtrack points, numerical labels related to cut invocations etc, like in [Bil90, dV89, SGS + 10, And03]. Some approaches require transforming programs into a special syntax [Bil90,KK14], or restrict the class of programs dealt with ([KK14] requires so-called cutstratification). Some approaches describe only approximations of the semantics.…”
Section: Introductionmentioning
confidence: 99%
“…The semantics of [SGS + 10] does not distinguish success from failure, as the purpose of the semantics is termination analysis. The semantics of [KK14] may describe answers which actually are not computed; such inaccuracy is acceptable as the semantics is intended as a basis for abstract interpretation, which introduces inaccuracies anyway. Of course such semantics is inadequate for reasoning about program completeness.…”
Section: Introductionmentioning
confidence: 99%