Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!unido!iaoobelix!wagner
From: wagner@iaoobelix.UUCP
Newsgroups: comp.lang.prolog
Subject: Re: Out of Stack - (nf)
Message-ID: <7000008@iaoobelix.UUCP>
Date: Fri, 26-Jun-87 08:22:00 EDT
Article-I.D.: iaoobeli.7000008
Posted: Fri Jun 26 08:22:00 1987
Date-Received: Sat, 4-Jul-87 18:56:17 EDT
Lines: 25
Nf-ID: #N:iaoobelix:7000008:000:1008
Nf-From: iaoobelix!wagner    Jun 26 13:22:00 1987


This is in response to Lan See Chen's <dalcs!chen@seismo.css.gov> article of
June 22nd, 1987:

You can call vanilla CProlog with the following options:

	-H N   heap allocation is N K bytes
	-G N   global stack allocation is N K bytes
	-L N   local stack allocation is N K bytes
	-T N   trail allocation is N K bytes
	-A N   atom area allocation is N K bytes
	-X N   auxiliary stack allocation is N K bytes
	-q     don't print name of restored file

An optional last argument specifies the CProlog saved state to restore.
If you are working with CProlog+ (i.e. CProlog plus dynamic loading) you
may have a slightly different invocation syntax.

How far you can go with head, global stack and local stack depends on the
amount of swapping space available on your machine. I think, before you reach
any of the limits stated in CProlog, your Prolog will crash due to
insufficient swapping space.

Juergen Wagner,		     (USENET) ...seismo!unido!iaoobel!wagner
("Gandalf")			 Fraunhofer Institute IAO, Stuttgart