On 13.Jan.2003 -- 11:29 AM, Santiago Pericas-Geertsen wrote:
> From: "Joseph Kesselman" <[EMAIL PROTECTED]>
> >
> > I've been out of the office for a month, but my understanding is that we
> > currently have two to three branches active -- main line development
> > (HEAD), XSLT 2.0 prep/development ("xslt20"), and -- if I remember
> > correctly -- the xsltc folks had also forked off a branch for some of
> > their own early development, though that may have been folded back in by
> > now. (At some point, of course, all the changes have to be reconciled.)
> >
>
> The XSLTC folks are using the "xslt20" branch as well, so that should be a
> good starting point for Christian's work.
Thank you all for the encouraging words! Especially to Joe for the
great round up of the previous discussions.
I've checked out the xslt20 branch now and will work with that. I'll
be looking first into analysing the stylesheet to eliminate unused
templates (ie cannot match according to schema) and possibly
simplifying templates with the help of a schema. But don't hold your
breath ;-)
Later I hope to find time to look at pruning. But since that seems to
touch fundamentals, I'd like to have that with a lower priority.
BTW loading the xslt20 branch into eclipse finds some 3000 unused
imports and a number of "static method XYZ() from type Foo should be
accessed in a static way" eg
org.apache.xalan.client.XSLTProcessorApplet.java line 755:
m_trustedWorker.yield();
m_trustedWorker is of type Thread and
public static native void yield();
Most of that could be fixed automatically by eclipse requesting
"organize imports". If you care for a patch (and don't mind some
reordering of imports), I could send it.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
