Re: One-based indexes in XPath

> The woe for me however is having to counter the screams I'll no doubt get
> from the library-developer (Javascript) users & also the hassle of
> converting indexes on the external library side

This is the least problem you might have. Be ready to explain why an
xsl:variable cannot be modified...  :)




-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play






On Tue, May 20, 2008 at 12:25 PM, Justin Johansson <procode@xxxxxxxxxxx> wrote:
> Thanks to Colin, Michael et al. for your input on this issue.
>
> Personally I am not phased by 1 or 0 though I guess, after your advice, the
> XPath 1-based idiom is the one I may as well favor in order to make for a
> more seemless interface to my external XPath library.
>
> The woe for me however is having to counter the screams I'll no doubt get
> from the library-developer (Javascript) users & also the hassle of
> converting indexes on the external library side.  Anyway the hit was going
> to come from one side or the other (XSLT or Javascript) so I might as well
> go with the XPath 1-based index idiom and get over it.  Since a lot of the
> library side uses Javascript native code for Array functions, that will
> cost performance there but, oh well, so what; premature optimization is the
> root of all evil as someone once said.
>
> Sigh & thanks, Justin Johansson