On Dec 7, 2011, at 10:41 AM, Peter Bex wrote: > Actually, the main reason is that SSAX is a horrible mess which has > many completely unrelated procedures all mixed together. > There are several egg that provide different sets of procedures > from the SSAX project. Most eggs include all files from the SSAX > project to make it easy to update them, but they don't install them > all. > > The proper place to do this is in the sxml-serializer egg, and > we definitely should *not* be adding random procedures to sxpath.
In fact it's already in sxml-serializer, which is what I recommend you use. Please see http://api.call-cc.org/doc/sxml-serializer#sec:Changes_from_stock, in which it's described that srl:sxml->xml is in there but renamed to serialize-sxml. As Peter said, we took the SSAX project and split it into manageable chunks; the code that isn't used simply isn't compiled in. That was one way we adapted it to Chicken. Other ways were to regularize and improve some of the identifier names, make things more idiomatic, and in sxml-serializer's case, add some feature enhancements. Jim _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
