Anoop,
At 02:17 PM 1/22/2004, you wrote:
Thanks for your note. That put things into the right perspective. Yes, you
are true that we are trying to get too much out of XSL. My problem is due to
two nested loops and the position() value is different in these two loops.
A value of position() in an "outer loop" (which is not actually a loop) can
be bound to a variable and referenced inside the "inner loop" (also not
actually a loop). Thus both position() values can be returned.
But again, we haven't seen the problem, and I agree with Ken that you may
be jumping to conclusions about how to approach this problem. It's not that
you're trying to get too much out of XSL. It's just that you may be
insisting on hiking up the mountain when XSL gives you a really nice cable
car you can just ride to the top.
I have started looking into recursive template implementation to find a
solution to my problem there. If you have any sample for that, it will
definitely be helpful to start with. Thanks for your note.
There are plenty of samples in the XSL FAQ and Googleable. But if you
posted details about the actual problem here you'd get advice tuned to the
actual problem.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list