I've checked in an updated version of the substring function and added test to the build Previoulsy the substring function didn't handle invalid indices etc at all - an out of bounds eception was thrown Now you get back an empty string along the lines of the spec.
The W3 xpath spec def of substring is very confusing and I think inconsistent if not wrong. If you take a look at the example in the spec http://www.w3.org/TR/xpath#section-String-Functions you'll see what I mean. They don't treat 0, negative numbers and infinity in a consistent manner. (In the newer XPath 2.0 spec these are treated as errors) Eddie _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Jaxen-interest mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jaxen-interest
