At 10:59 AM 7/3/2003, Stuart wrote:
Although I accept that the inclusion of an <xsl:make-bacon-sarnie
burnt-to-a-crisp="yes"/> instruction would make a lot of programmer's lives
a lot more pleasant, it is clear to me that the functional nature of XSLT is
highly unsuited to cooking, which requires procedural, contingent, and
thread-based operations.
There are already a lot of questions on this list where people assume or try
to force procedural-style progamming out of XSLT, and a set of cookery
instructions would simply aggravate the matter.
This is true, but on the other hand XSLT (with appropriate extensions)
might be very well suited for ordering dinner in a restaurant.
<xsl:plate match="premier">
<xsl:apply-plates select="salad | pasta | $specials[(_at_)day=$today]"/>
</xsl:plate>
The details of how the food gets to the table could be left to the
implementation.
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