On Wed, Dec 07, 2011 at 05:35:37PM +0100, Christian Kellermann wrote: > > Why is it not included if it is there? > > > > Or why is there an sxml-serializer egg if the code is already part of > > the SSAX libs, which is part of the sxpath egg? > > As I understood the egg is just a wrapper around the upstream code. > I guess that the original author did not do a complete wrapping > here. If this is useful to you, we would not mind a patch enhancing > the sxpath extension.
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. (the *REALLY* proper way would be to drop SSAX and create a sane and consistent XML library from scratch, maybe reusing some algorithms from SSAX, but that's a whole other story...) Cheers, Peter -- http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users