> > If you want on-the-fly correct order, then the org.jaxen.expr.* package
> > is what you want.
>
> I would think, naively, that keeping order on the fly would be so you don't
> have to sort later... Not sure how the expression evaluation works though,
> how you 'visit' nodes...
Yah, on-the-fly would prevent resorting later. I'd just want to be sure
we don't add any overhead to non-union cases, where things end up in
the correct order anyhow, I think.
The expressions are self-visiting. Call evaluate(...) on an expression,
and it'll walk its sub-components (by calling evaluting(...)) as needed.
Obviously, there is a short-circuit with 'or' so that the RHS doesn't
get touched unless the LHS is false, etc.
We don't use a Visitor pattern for evaluation of the expressions.
(Though, they may be Visitable, but that's not part of the eval.)
> > Coordinate edits to the expr.* package on the list, becuase I know
> > someone else is in there right now trying to fix a predicate bug, too.
>
> Thx. Don't assume I'll get anywhere with this in a reasonable amount of
> time... I'm just a dilettante...
Go ahead and blurp me your sf.net username, and I'll set you up to do
developer CVS access. Your karma follows you from jakarta.apache.org,
of course.
-bob
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
