Detecting Infinite Looping

Subject: Detecting Infinite Looping
From: "W. Eliot Kimber" <eliot@xxxxxxxxxx>
Date: Wed, 28 Jan 1998 22:45:49 -0600
I'm in the process of implementing HyTime location address resolution. One
of the possible error conditions is a circular reference where one location
address directly or indirectly addresses itself.  This is a reportable
HyTime error, for obvious reasons.  My question is this: how would I go
about detecting such a case in DSSSL? 

My logic constructs a node list by recursively processing each location
address found. How would I compare each new node to the node list at that
point to see if it's already in it (if it's a location address)?

Thanks,

E.
--
<Address HyTime=bibloc>
W. Eliot Kimber, Senior Consulting SGML Engineer
Highland Consulting, a division of ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 95202.  214.953.0004
www.isogen.com
</Address>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist


Current Thread
  • Detecting Infinite Looping
    • W. Eliot Kimber - from mail1.ability.netby web4.ability.net (8.8.5/8.6.12) with ESMTP id XAA26840Wed, 28 Jan 1998 23:49:20 -0500 (EST) <=
      • Richard Light - from mail1.ability.netby web4.ability.net (8.8.5/8.6.12) with ESMTP id EAA04376Thu, 29 Jan 1998 04:14:50 -0500 (EST)
      • Henry Thompson - from mail1.ability.netby web4.ability.net (8.8.5/8.6.12) with ESMTP id EAA04681Thu, 29 Jan 1998 04:40:15 -0500 (EST)
      • <Possible follow-ups>
      • Pawson, David - from mail1.ability.netby web4.ability.net (8.8.5/8.6.12) with ESMTP id DAA29108Thu, 29 Jan 1998 03:02:52 -0500 (EST)
      • Gavin Nicol - from mail1.ability.netby web4.ability.net (8.8.5/8.6.12) with ESMTP id FAA05174Thu, 29 Jan 1998 05:37:26 -0500 (EST)