Tom said:
One thing is that debugging xslt problems takes some
experience, and can seem rather different than debugging,
say, javascript. In practice, I have found that as I get
better at diagnosing my xslt problems, I have gotten better
at debugging javascript and python too. I think that you
need to apply more flexibility for diagnosing and correcting
xslt problems and enhancing that ability is useful everywhere else.
If people would like to recount their debugging experiences and methods,
I'll collate them for the faq?
regards DaveP
-
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.
RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list