PROLOG OPERATOR TESTS
       Written by Chris Moss, Dept. of Computing, Imperial College
                      Contributed by Norbert Fuchs,
            Department of Computer Science, Zurich University
                   Shelved on the 3rd of October 1988



This entry comes as two files: this one (OPTEST.PRE), and the source
(OPTEST.PL).


To run the tests, execute the predicate
    optest
supplying full description  of system used (with version)  as the second
parameter.

If necessary  delete any  clauses which  give syntax  errors but  do NOT
change  them in  any  way (spaces  may be  crucial).  Skip any  run-time
errors.

You may  change the operator declarations  if your system  has different
conventions.  e.g.  If  your  operator precedence  is  in  the  opposite
direction then  you may add some  suitable constant to ALL  the operator
priorities.

Thanks to Hamish Taylor  for some of these tests. Note  that some of the
answers are definitely WRONG. I leave you to decide which!

These are the results I [Chris  Moss] already have (first letter of each
message):

Version \ Test        1 2 3 4 5 6 7 8 91011121314151617181920
CProlog 1.5           M P - S - M S P A A A - N N P R D L N
Quintus 2.0           M P - S C M S P A A A - N N P N D L N
MACProlog 2.0         M P - S L L - P A A A - N N P R D L S
Poplog 9.3            D S P P R R S S P S P P N P - R - - -
MuProlog 3.1db        M P P P R R P P P P P P P P P R - - -



CHECKED ON EDINBURGH-COMPATIBLE (POPLOG) PROLOG :
    Yes.


PORTABILITY :
    That's what it's meant to test!


INTERNAL DOCUMENTATION :
    Each test carries a very brief statement of its purpose.