🚀 go-pugleaf

In article <1990Aug29.095308.18522@sics.se> roland@sics.se (Roland Karlsson) writes:
\\\
>the trail will be effected at !.  So at backtracking (untrailing) you
>will trap at the pointer to the heap.  The code on the heap will be
>executed and thereby the old value restored.  So a ! will NOT make
>the change permanent.

Oh. From your previous post I presumed we had implemented the same
thing, but apparently not quite.

The version of setarg/3 I have uses the *stack* to remember the
fact that a given argument (i.e. part of the term structure
stored on the heap) has been changed -- in this respect it's just
like other backtrack points.

A cut therefore will forget the fact that the change was done
and therefore it *won't* be restored on backtracking.

We have the possibility of doing things like communicating
between alternatives in a disjunction, or implementing arrays
(does Sicstus allow large arities for structs -- it's
a bit hard to do (e.g. in "copyterm" -- part of the assert/clause
mechanism) everywhere)? This comes in handy for implementing
bagof/3, etc.

I realize this is all a bit nasty, and use of setarg/3 is open to abuse, 
but at the moment the system I have is only for my use (and if you saw the 
state of the documentation it would be obvious why).

-Kym Horsell