Hi, 

The Prolog to SQL compiler is packed into one uuencoded compressed
tar file named

   prolog_sql_comp.tar.Z.uue

Under UNIX you must uudecode and uncompress it to get the directory
prolog_sql containing the files 

   README.txt               - this file
   SQLCompiler.pl           - eclipse Prolog sources
   PrologSQLCompiler.ps     - a PostScript file of the 
                              report

The Prolog to SQL compiler sources here are for Eclipse Prolog of ECRC - but 
porting them to e.g. Quintus should not be a problem.

   Some hints:

   - init_gensym/1 is subsumed by gensym/2 in Quintus. gensym/2 is
     needed by the compiler to generate unique variable idenfiers
     and alias names for relation tables. 

     Check in the libraries whether gensym/2 exists (in Quintus,
     it's in the strings library); otherwise, you will have to
     implement it yourself.

   - cpu_time/[1,2,3] are needed for the benchmarks only, the compiler
     does not need it. The code for cpu_time was taken from R.A.O'Keefe's
     book "The Craft of Prolog"

   - Expert Systems PD Prolog (at least in the non-DEC10 mode) does not
     like the % comment lines

To run the compiler with some prepared examples, enter the goal

   ?- benchmark(N,No,D).

with N the number of times you want the compilation done, No the number
of the benchmark (1,...,7), and D the time in milliseconds/ticks/seconds.


Report:

The report is provided as a uuencoded compressed Postscript file. 
(approx. 133 KB) This should be printable by almost all UNIX machines (I tested 
it on our SUNs) in the following sequence of steps:

   uudecode PrologSQLCompiler.ps.Z.uue
   uncompress PrologSQLCompiler.ps
   lpr PrologSQLCompiler.ps

If this doesn't work, please let me know. I can always send you a paper
copy if you give me your exact postal address.


Remarks:

I am very interested in any feedback on the compiler, especially in

   - adaptations needed to make it run under your Prolog system,
   - error reports,
   - and the applications in which you (plan to) use the compiler

Especially the first point is important for me - it will help me help other
users - and perhaps even allow me to have the appropriate "compatibility"
packages right away, saving you some work...

Thanks for your cooperation,

Christoph


