so if anything particularly useful (for other people) turns up in "xitomatl non-ported-stuff" it should be grabbed and made stable somewhere else, like maybe in a srfi or something?
On Thu, May 28, 2009 at 7:58 AM, Derick Eddington <[email protected]> wrote: > On Thu, 2009-05-28 at 06:21 +1000, Ramana Kumar wrote: >> Are the xitomatl libraries / tools documented? > > No. As the README says: > > See the test programs in the "tests" folder for examples of how > to use the libraries. > > [...] > > Disclaimer: > ----------- > My libraries are a moving target. I'm continually changing > things. Other people's libraries I've assimilated should be > stable and should need to be changed only for bug fixes and > updates to new versions. If in the future some of my libraries > stabilize, I'll advertise that and make documentation. > > Continually revising documentation would bog me down. Documentation > which actually helps is difficult and very time consuming to make (IMO). > I already know how it all works! :) I try to make good commit logs, and > so reading through them will help someone familiarize with the > collection. As always, read the source :) I don't even know where > Xitomatl is going. People should consider it my laboratory. > >> Do you know if there are many users? > > I have no idea. I don't think so. I think a few people use a few of > the ports of other people's libraries and leave all my stuff alone. > That's what I recommend. I suggest the ports to people because they are > stable (from my end) and are documented somewhere or are otherwise > familiar. When I mention my own stuff, I offer it as only an example > you might consider for your own toolbox or study. I think some of my > stuff is pretty useful and I'm trying to build a framework for me to use > in the long-term for my own real-world projects, and I very much intend > to always have it as something I can change on a whim. > > -- > : Derick > ---------------------------------------------------------------- > >
