The role of frame-based representation in reasoning
Communications of the ACM
Artificial Intelligence
Prolog: a relational language and its applications
Prolog: a relational language and its applications
Communications of the ACM
Conformational analysis using a simplified tms implemented with object-oriented and logic programming
An interpreter for large knowledge bases
CSC '89 Proceedings of the 17th conference on ACM Annual Computer Science Conference
An extension of PROLOG for object-oriented programming in logic
IEA/AIE '90 Proceedings of the 3rd international conference on Industrial and engineering applications of artificial intelligence and expert systems - Volume 2
CSC '90 Proceedings of the 1990 ACM annual conference on Cooperation
Multiparadigm research: a new direction of language design
ACM SIGPLAN Notices
Integrating logic and object-oriented programming
ACM SIGPLAN OOPS Messenger
The promise of multiparadigm languages as pedagogical tools
CSC '93 Proceedings of the 1993 ACM conference on Computer science
DrScheme: a programming environment for Scheme
Journal of Functional Programming
I+: A multiparadigm language for object-oriented declarative programming
Computer Languages
| Hi-index | 0.00 |
A description is given of an interface that was developed between Loops and Xerox Quintus Prolog. Loops is an extension to the Xerox AI environment to support object-oriented programming; Xerox Quintus Prolog is a version of Prolog that runs on Xerox Lisp machines. Such a bridge enables all the support tools of both environments to be accessed, and degradation of performance that occurs when one language is implemented top of another is avoided. The interface has three layers. At the lowest level, a set of Prolog predicates gives the Prolog programmer access to Loops objects. This lowest level is the bridge from Prolog to Loops. At the next level, programming tools in the Loops environment let object methods be defined in Prolog. At the highest level, the Prolog programmer can treat Prolog clauses as Loops objects that can be manipulated outside the Prolog database. Each layer can be used independently.