Yeah, this is one reason why I've put myself in the habit of slapping a
string() function around something I expect to be a string, a boolean()
function around booleans, etc.
More warnings would be good too :)
Simon
On Tuesday, May 20, 2003, at 06:36 PM, Michael Kay wrote:
Two good examples here of why it's good language design to be rather
stricter about error checking. Type checking of course comes into this
category as well. The "anything goes" style of XSLT 1.0 is great when
you get things right, but can be a pig to debug when you get things
wrong.
--
anti-spam: do not post this address publicly
www.simonwoodside.com -- 99% Devil, 1% Angel
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list