feeeh@minyos.xx.rmit.oz.au (Elizabeth Haywood) (11/02/90)
We have recently purchased arity/prolog and I would like to know if anyone has experience of using this package with students or to develop an "expert" system. thanks liz haywood
wdh@linus.mitre.org (W. Dale Hall) (11/14/90)
Here's a problem I've encountered using ARITY/PROLOG, in trying to employ Turbo C (v2.0) to do some graphics output. I've gotten both the prolog code and C code to compile to .OBJ modules, and when I try to link, my linker complains that each module wants to set up its own stack, and says something like "duplicate stack" and refuses (I assume properly) to create an .EXE file. Oddly enough, when I write a small test program to see whether the problem is more basic (i.e., I have the C module simply do some arithmetic and return some value), everything is just hunky-dory. Apparently, my use of the stack is really the culprit. According to the ARITY manual, there is supposed to be a file called "arityc.c" which sets up memory usage (and which I hope does the identification of the prolog stack with the C stack, or at least makes the duplication somehow tolerable) for prolog and C. This file was supposed to be included with my UTIL disk, but it doesn't appear in either the 5.25" or the 3.5" version. Has anyone else faced/overcome this problem? I've honestly RTFM'ed until I can't, and don't have the ability (without a lot of intermediate bother) to contact the ARITY bbs. Any suggestions would be welcome. Dale.
weiss@theory.lcs.mit.edu (Paul G. Weiss) (11/15/90)
The ARITYC.C file which you mentioned has been superceded by the STARTUP.C file, which is the standard startup for Arity/Prolog programs. Without this file, the stack segment will be found in the ARITY.LIB library, with it, the stack segment will be found in the C libraries.