🚀 go-pugleaf

> So it's come to this -- destructive assignment in Prolog!

> There are several methods for implementing arrays in Prolog
> and the one I have implemented is a variant of the setarg/3
> precicate that also appears elsewhere.

> setarg(Index,Term,Value)

> replaces argument ``index'' in ``term'' with ``value'' but
> allows backtracking so that ``term'' may be restored to its
> former state -- no destructuve assignment happens unless you
> 	setarg(X,Y,Z), !.

Setarg/3 is implemented in SICStus Prolog.  But 'setarg,!' will NOT
lead to a destructive assignment.  The correct value is reinstalled
att backtracking.  I would consider it a bug if it did so.

( There is SECRET an DANGEROUS system setarg/4 that can do destructive
  assignment.  Non experts on SICStus implementation shall NOT use it.
  Please don NOT tell anybody (;-) )

Roland Karlsson

PS. I agree that Prolog should benefit from having some unclean data types,
such as arrays, global variables etc.  All with destructive assignment.
They should be typed or (as in ESP Prolog) defined as some type at
creation. (X=1 will give you a normal term X and Y:=1 will give you an
unclean variable Y that can be changed to an other value of compatible
type but any atempt to unify it with anything but itself will fail. That
is 'A:=1,B:=1,A=B' will fail but 'A:=1,B:=1,A==B' and 'A:=1,A=A' 
will succeed.)
--
Roland Karlsson
SICS, PO Box 1263, S-164 28 KISTA, SWEDEN	Internet: roland@sics.se
Tel: +46 8 752 15 40	Ttx: 812 61 54 SICS S	Fax: +46 8 751 72 30