Subject: Re: [xsl] Unexpected result from <a href="...">...</a> in some cases From: Quinn Taylor <quinntaylor@xxxxxxx> Date: Tue, 19 Aug 2008 21:18:24 -0600 |
Ken, thanks so much for taking the time to help out. Sure enough, your solution works as advertised. :-)
One thing I'd like to simplify/optimize is the number of recursive descents. It seems that your code recurses all the way down to the base case and back up for each path element to correctly construct the parent href. This is certainly not an O(n^3) algorithm, but it seems like a triangular number (http://mathworld.wolfram.com/TriangularNumber.html ). For very long paths, this creates more work than necessary. Even so, I'll take what works over what doesn't. :-)
- Quinn
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Unexpected result from <a, Quinn Taylor | Thread | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Re: [xsl] Unexpected result from <a, Quinn Taylor | Date | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Month |