Hi Dave,
I had a chance to look over the EXSLT website and here's what I found. Of the modules that have implementations (common, math, sets, and strings) the strings module is the only one that is missing some functions. Then there are three modules that do not have any implementations at all (dates-and-times, dynamic, and regular-expressions). To me I think it would be nice to finish off the strings module and then move on to the others. The remaining strings functions are encode-uri, decode-uri, tokenize, split, and replace. I think that replace will be the hardest out of this group, the rest seem pretty straigh forward. The split and tokenize functions need to return xml nodes of the tokens found, my understanding is that this functionality is being developed, is that correct? As far as the test cases, does Xalan-C++ use the same smoketest stylesheets that Morris said were in the test/tests/extensions/library directory or is there another directory? I would like to see some existing examples so that I can get the structure and layout correct. -Corey > > Hi Corey, > > Why don't you take a look at the EXSLT web site and compare what's > implemented in Xalan-C to look for gaps? I'm a little fuzzy on the > details, but there are quite a few things that aren't > implemented yet, so > why don't you look for something that looks interesting, and > we can go from > there. If you can come back with a potential list, we can figure out > priorities, etc. > > We should also spend some time devising basic stylesheets > that will test > the EXSLT functionality. We'll need at least a set of smoketest > stylesheets before we start claiming we're really implementing EXSLT. > > Dave > >
