2011
DOI: 10.1007/978-3-642-18378-2_8
|View full text |Cite
|
Sign up to set email alerts
|

On the Portability of Prolog Applications

Abstract: Abstract. The non-portability of Prolog programs is widely considered one of the main problems facing Prolog programmers. Although since 1995, the core of the language is covered by the ISO standard 13211-1, this standard has not been sufficient to support large Prolog applications. As an approach to address this problem, since 2007, YAP and SWIProlog have established a basic compatibility framework. The aim of the framework is running the same code on Edinburgh-based Prolog systems rather than having to migra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
10
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
3
3
1

Relationship

4
3

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 12 publications
0
10
0
Order By: Relevance
“…It was later ported [19] to the SWI [21] engine via a complete re-write of the C code. This has become the main development code as YAP provides a comprehensive compatibility layer to SWI's C interface [20]. The library and examples presented here can be downloaded from our website (http://bioinformatics.…”
Section: Discussionmentioning
confidence: 99%
“…It was later ported [19] to the SWI [21] engine via a complete re-write of the C code. This has become the main development code as YAP provides a comprehensive compatibility layer to SWI's C interface [20]. The library and examples presented here can be downloaded from our website (http://bioinformatics.…”
Section: Discussionmentioning
confidence: 99%
“…One obvious advantage is that it helps accommodate the programmer's need for syntactic sugar, while keeping changes in the kernel language at a minimum. It also offers benefits for portability, since it makes it possible to keep a common front end (or a set of language features) and plug in different kernel engines (e.g., Prolog systems) at the back end, as long as they provide access to the same kernel language (or one that is rich enough) [15].…”
Section: Discussionmentioning
confidence: 99%
“…A post in the ALP newsletter, Bagnara (1999) pointed out that many implementations differed from the standard in at least some way, and that those differences were poorly documented. Other shortcomings were pointed out by several Prolog system main contributors, such as, e.g., by Carlsson and Mildner (2012), Diaz et al (2012), and Wielemaker and Costa (2011). However, both aspects, adoption of the core standard and precise documentation of where each system departs from the standard, have improved progressively.…”
Section: The Iso Standard and Portability Of Prolog Codementioning
confidence: 99%