Re: Feature Request - Node Set Processing (long)

["G. Ken Holman" <gkholman@xxxxxxxxxxxxxxxxxxxx>]

At 99/01/18 09:33 +0700, James Clark wrote:
>"G. Ken Holman" wrote:
>
>> (4) - so, I need to walk the source tree at each level of interest and
>> determine if where I am (or my ancestor module is) is where I was before I
>> started walking, and at each step render different information calculated
>> from where I am walking:
>...
>If XSL had local constants/variables, you could express exactly that
>algorithm:
>...
>   <xsl:constant name="current-node-name" value="{@id}"/>

Thanks ... while the code would work in my situation where I have unique ID
attribute values, how would one identify nodes where such attributes are
unavailable?

......... Ken

--
G. Ken Holman         mailto:gkholman@xxxxxxxxxxxxxxxxxxxx
Crane Softwrights Ltd.  http://www.CraneSoftwrights.com/s/
Box 266,                                V: +1(613)489-0999
Kars, Ontario CANADA K0A-2E0            F: +1(613)489-0995
Training:   http://www.CraneSoftwrights.com/s/schedule.htm
Resources: http://www.CraneSoftwrights.com/s/resources.htm
Shareware: http://www.CraneSoftwrights.com/s/shareware.htm
Next XSL Training (see training link):   WWW8 - 1999-05-11


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list