From ok@atlas.otago.ac.nz  Fri Sep 22 04:33:49 2000
Received: from atlas.otago.ac.nz (atlas.otago.ac.nz [139.80.32.250])
	by swi.psy.uva.nl (8.9.3/8.9.3) with ESMTP id EAA24006
	for <prolog@swi.psy.uva.nl>; Fri, 22 Sep 2000 04:33:47 +0200 (MET DST)
Received: (from ok@localhost)
	by atlas.otago.ac.nz (8.9.3/8.9.3) id OAA02449;
	Fri, 22 Sep 2000 14:34:03 +1200 (NZST)
Date: Fri, 22 Sep 2000 14:34:03 +1200 (NZST)
From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
Message-Id: <200009220234.OAA02449@atlas.otago.ac.nz>
To: p.singleton@keele.ac.uk, prolog@swi.psy.uva.nl
Subject: Re: Circular references
Cc: ok@atlas.otago.ac.nz

	> Any cyclic term can be handled this way, by adding suitable equations
	> to the body.  You will find it hard to write the code that does that,
	> but that should make it a bit clearer why cyclic terms are a BAD THING.
	
	I don't accept that the inelegance of a workaround generally indicates
	that one is trying to do a bad thing (e.g. create zero-length arrays
	in Visual Basic) so please explain why it does in this particular case.
	
It is not the existence of the workaround that proves cyclic terms are
a bad idea, nor its "inelegance" (nowhere did I say or imply that the code
would be inelegant), but the DIFFICULTY of writing ("HARD to write") the
code that manipulates cyclic terms.

You could have refuted that claim by writing the code in a short time,
posting it, and saying how easy you found it.
	

