RE: Using Saxon 8.5 and collection() to process a dir
18.1.2 says: "There is no prohibition on calling extension functions that have side-effects." There's nothing that limits the nature of the side-effects. (Incidentally, a rather more questionable extension function is saxon:try(), which catches errors in evaluating its parameters. This is really a pseudo-function. However, the basic principle is that a user who uses extension functions knows that they are sacrificing portability, and I'm prepared to interpret the spec liberally if it's the only way to deliver functionality that users need. If you don't like it, don't use the extension.) Michael Kay > -----Original Message----- > From: Colin Paul Adams [mailto:colin@xxxxxxxxxxxxxxxxxx] > Sent: 04 August 2005 19:25 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: Using Saxon 8.5 and collection() to > process a directory of XML files > > >>>>> "Michael" == Michael Kay <mike@xxxxxxxxxxxx> writes: > > Michael> Extension functions are allowed to do what they like, > Michael> including causing standard functions to behave in a > Michael> non-standard way. Caveat invocator. > > Where does it say this? I can't find anything. > -- > Colin Adams > Preston Lancashire
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format