Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Deprecating XSLT templates
 Mode changing can be a nice way of commenting out template rules, I agree. Except that it sounds like he's talking about named templates, not template rules. If there's a stylesheet, say, that contains many named templates that function essentially as subprocedures to be used by importing or including stylesheets, then it is an API, I guess. Deprecation implies that the named template should still work, but should notify the stylesheet writer that, for now on, you should use a different named template. <xsl:message> could work, as long as you can ensure that your developers are using implementations that will always flag the message for them, and also that the message does not interfere with pre-existing calls to that template. If you can satisfy both of these conditions, I suppose it would be a reasonable solution. Tim, is there something about it that doesn't satisfy you? Evan Lenz elenz@x... http://www.xyzfind.com XYZFind, the search engine *designed* for XML Download our free beta software: http://www.xyzfind.com/beta -----Original Message----- From: xml-dev-errors@l... [mailto:xml-dev-errors@l...]On Behalf Of Mike Brown Sent: Thursday, October 05, 2000 2:47 PM To: Mike Brown; 'John Prout' Cc: 'xml-dev@l...' Subject: RE: Deprecating XSLT templates I forgot to mention an even better option -- simply change the mode! <xsl:template match="foo" mode="deprecated"> If you never explicitly do an xsl:apply-templates with that mode, it will never match a node. 
|
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
|
|||||||||
