Hey Mark,
Sorry, I've been incredibly busy with work these days, so I haven't had
lots of time to look at possible patches.
A pain isn't it! I guess you haven't had chance to take a look yet?
Is there any chance you could adapt the exslt-regexp patch to work with
Xerces-C's regular expression implementation? That would be far better
than requiring boost, since Xerces-C is guaranteed to be there. Another
choice would be to support both, with a fallback to Xerces-C if boost is
not available, or not desired.
It would be possible. It seems that they are probably not the same, but
I doubt it matters too much (AFAICS exslt is extremely loosely
specified, and the basic syntax of the regular expressions is the same,
so it's going to make most people happy I would have thought).
>
This seemed to have got lost (at least, I haven't seen it appear on
the list in about 24 hours -- I apologise if this is duplicated).
In the meantime, I've also implemented the rest of exsl:dyn &
exsl:random.
Dyn:
http://www.blushingpenguin.com/mark/xalanc/exslt-dyn.patch
Random:
http://www.blushingpenguin.com/mark/xalanc/exslt-random.patch
random:random-sequence doesn't seem very well defined (returns
number+, which presumably means nodeset). I attempted to follow the
only other implementation I could find -- that of the EXSL.NET
implementation.
dyn and random are trickier, and random is still under-specified (there
was some discussion on the EXSLT list about this at least 3 years ago).
I'd like to make sure the implementation is clean, but is also
flexible. Hopefully, I can find some time in the next 3 weeks to look
at the patches.
dyn seemed ok to me. Were you thinking of anything specific?
random roughly follows an implementation of EXSLT for .NET (can't
remember where that was exactly). I couldn't find another one.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
