Noah Lavine <noah.b.lav...@gmail.com> writes: > Hello, > >>> I think it would make sense to include ‘fmt’ in core Guile only if the >>> API is reasonably stable and there are infrequent upstream releases, so >>> we don’t quickly end up shipping an old incompatible version. >> >> Agreed, and I don't know if this is the case or not. >> >> I would add on another criteria, that we should avoid adding modules to >> Guile unless they are to be used in Guile itself. For everything else, >> there is our CPAN that we need to make -- it will provide more freedom >> both for module authors/packagers and for users. > > This makes sense, but I think there is an important distinction to > make that we do not currently make. We should have a clear idea of > what modules are used by Guile, so we can get a "minimal" Guile when > we want it, for instance for embedding into other applications. > +1! Racket has acquired a problem with that over the years, and there are now efforts to rectify it [0].
[0] http://www.mail-archive.com/dev@racket-lang.org/msg02376.html > However, it would be great if the standard install of Guile included > lots of modules, such as htmlprag, because it is nice to have the > batteries included when you are programming. > My opinion on that is that if it's really easy to install additional libraries (which is not yet the case, unfortunatly!), there would be no need to bundle additional stuff not needed by the core into Guile releases. Regards, Rotty -- Andreas Rottmann -- <http://rotty.yi.org/>
