How should Prolog computation Be represented for practical use?

We propose a visual computation model called theBox and Plane Model (BPM), which visually clarifies the semantics of backtracking, the cut operator, and side-effects, thus allowing the procedural features of Prolog to be grasped. On the bases of the BPM, we developed a visual debugger for Prolog, PROEDIT2, which has proved that this kind of pragmatic computation model for Prolog increases the efficiency of the debugging work.

[1]  Ehud Shapiro,et al.  Algorithmic Program Debugging , 1983 .

[2]  John B. Johnston,et al.  The contour model of block structured processes , 1971, SIGP.

[3]  Nan C. Shu,et al.  Visual Programming: Perspectives and Approaches , 1989, IBM Syst. J..

[4]  Robert A. Kowalski,et al.  Predicate Logic as Programming Language , 1974, IFIP Congress.

[5]  Robert A. Kowalski,et al.  Logic for problem solving , 1982, The computer science library : Artificial intelligence series.

[6]  J. A. Robinson,et al.  Logic programming —Past, present and future— , 1983, New generation computing.

[7]  Masayuki Numao,et al.  Visual Debugger for Prolog , 1985, CAIA.

[8]  Margaret M. Burnett,et al.  Visual Programming , 1995 .

[9]  John Wylie Lloyd,et al.  Foundations of Logic Programming , 1987, Symbolic Computation.

[10]  Masayuki Numao,et al.  Prolog Computation Model BPM and its Debugger PROEDIT2 , 1986, LP.

[11]  Luís Moniz Pereira.  Rational Debugging in Logic Programming , 1986, ICLP.

[12]  William F. Clocksin,et al.  Programming in Prolog , 1981, Springer Berlin Heidelberg.

[13]  Marc Eisenstadt,et al.  Graphical Debugging with the Transparent PROLOG Machine (TPM) , 1987, IJCAI.