Alan Manuel Gloria: > In short: this is a lot of work for little gain (specifically, so that > use-modules will work correctly on Guile 2.0 when autocompilation is > turned OFF). We can just say that currently, on Guile 2.0, > autocompilation (the default) needs to be enabled in order to work > properly.
That sounds perfectly reasonable. Thanks for tracking that down. In the longer term, maybe we can convince the guile folks to add another hook. For the moment, I've noted that in the tutorial. We need to set things up so that this stuff is easy to install. An obvious approach is to autoconfiscate this thing, so that the libraries are installed system-wide, as well as sweeten, unsweeten, and whatever else. We probably need an uncurly and unneoteric as well. At that point, people who don't use guile can still use the tools, treat the "un*" programs as compilers, and use make (or similar). Where we can make it more automatic (e.g., auto-load ".sscm") we should strive to do so. (If you have an autotools allergy, let me know, but they're the obvious way to do this.) --- David A. Wheeler ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
