ftp.nice.ch/peanuts/GeneralData/Usenet/news/1989/CSN-89.tar.gz#/comp-sys-next/1989/Oct/Prolog-ported-to-NeXT-machine?

This is Prolog-ported-to-NeXT-machine? in view mode; [Up]


Date: Sun 25-Oct-1989 15:06:04 From: Unknown Subject: Prolog ported to NeXT machine? Does anyone have any information on a version of Prolog that has been ported to NeXT 1.0 ? (Or even NeXT 0.9 if source is available!) I have looked at both CProlog and nuprolog and neither can be trivially ported. Thank you, Anne Louise Gockel Cornell Computer Science >From: louie@sayshell.umd.edu (Louis A. Mamakos)
Date: Sun 30-Oct-1989 09:35:03 From: Unknown Subject: Re: Prolog ported to NeXT machine? In article <33531@cornell.UUCP> alg@cs.cornell.edu (Anne Louise Gockel) writes: >Does anyone have any information on a version of Prolog that has been >ported to NeXT 1.0 ? Has anyone looked at BerkeleyPrologSystem (anonymous FTP from ucbarpa.berkeley.edu)? -=EPS=- >From: epsilon@wet.UUCP (Eric P. Scott)
Date: Thu, 26-Oct-1989 18:09:52 From: Unknown Subject: Re: Prolog ported to NeXT machine? >From: Jeff Schultz <munnari!jws@uunet.UU.NET> In article <33531@cornell.UUCP> you write: > I have >looked at both CProlog and nuprolog and neither can be trivially ported. I wrote most of NU-Prolog, so I'm interested to know about port problems. NeXT aren't marketing in Australia so I've no first-hand knowledge of them. Would you summarize the problems you found? Jeff Schultz, jws@cs.mu.oz.au ----------------------- With a few changes NUProlog compiled on the NeXT system. However it would not run at all. Indeed it would not even get to the first statement in main(). I suspect, but have not confirmed, that the problems are related to the fact that NUProlog has it's own malloc routines. ****************************************************************************** SBProlog (public domain, available from arizona.edu) compiled and ran with only a couple changes: sim/init.c: remove 'extern char *malloc();' sim/loader.c: remove 'extern fread();' sim/parse_operand.c and sim/print_inst.c: put include statement for "sim.h" before include for "inst.h" I've been told that compiled SBProlog code runs reasonably quickly, but as an interperter, SBProlog is fairly slow. >From: scott@sage.uchicago.edu (Scott Deerwester)

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.