For some reason after I updated to get the patches I had just submitted I ran into a new problem-- curious.
In runes/ystream.lisp line the reader macro #/ is used, which I tracked down to being defined in runes/syntax.lisp. I added this dependency to cxml.asd and now it works fine for me. Not sure why this just came up and I (or anyone else) didn't run across this sooner.
Here's a patch for it. After I recorded the patch I reverted and tried it again, this time I didn't have any problem. I deleted all the fasls, still didn't have a problem. Very curious.
The dependency still exists between runes/ystream.lisp and runes/syntax.lisp so I think this is still good to state explicitly in the asd rather than getting lucky on the order it loads.
Nathan
-----Original Message----- From: David Lichteblau [mailto:david@lichteblau.com] Sent: Monday, January 23, 2006 5:12 PM To: Nathan Bird Cc: cxml-devel@common-lisp.net Subject: Re: [cxml-devel] flush-ystream on character-stream-yestream
Quoting Nathan Bird (nathan@acceleration.net):
;;this end argument had been missing. :end (ystream-in-ptr ystream))
Oops, thank you. Committed to CVS.
BTW, I've been playing around with using CXML to generate XUL, since it mixes with HTML and namespaces matter and all that jazz. As an interesting comparison I tried generating and serializing out through UnCommon Web a
big
html table with a lot of dynamic generated strings in it. It looks like doing it with CXML is about 2.5 times faster than doing the equivalent
with
UCW's own tool-- yaclml. Sweet!
That's good to know. My own changes have been more about correctness and features, but it's obvious that Gilbert put some thought into optimizations.
(Although the DOM functions are inherently complex and rather slow compared to the actual parser. For example, parsing with xmls-compat is dramatically faster than parsing into DOM.)
David