On Mon, 14 Jan 2002, Tod Harter wrote: > Not sure I entirely agree with you on that one Matt. XSLT is declarative, and > thus a lot of people who are used to procedural programming aren't going to > like it much, but there is a HUGE amount of expressiveness possible in a > declarative syntax, if you can wrap your head around it. Once you do its good > stuff, as any LISP or Prolog guy can tell you. SAX is good for some things, > XSLT is good for others. The nice thing is that one can apply either tool > when its appropriate. The framework should make that as painless as possible.
I do agree. There's a bug. Someone just needs to fix it. Shouldn't be too hard - the framework handles all this stuff for you. The bug is in XSP.pm, throwing away prior transformations if the code is compiled and the file's mtime hasn't changed. Hope someone has fun finding it! -- <!-- Matt --> <:->Get a smart net</:-> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
