JPL 3.x Objectives
- enable Prolog applications to exploit any Java classes, instances,
methods etc. (without requiring any wrappers, metadata etc. to be set
up first)
- enable Java applications to manipulate any Standard Prolog libraries,
predicates, etc. (without requiring any wrappers, metadata etc. to be
set up first)
- enable hybrid Prolog+Java applications to be designed and
implemented so as to take best advantage of both language systems, and
to be testable, debuggable, maintainable etc.
- minimum impact deployability:
runtime support for Prolog+Java apps must be a position-independent,
self-sufficient filestore tree, requiring no changes to registries,
system libraries, system configuration files etc.
- minimum dependency deployability:
as with JVMs, the Prolog+Java runtime support must depend upon nothing
which cannot be taken for granted in healthy OS installations
- minimum vulnerability deployability:
the Prolog+Java runtime support must be immune to legitimate variations
in its environment (PATH settings, other applications and libraries
including other Prolog+Java apps, etc.)
- (to be developed...)
Paul Singleton
drafted 19th February 2004