Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Ian Hulin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/01/11 11:21, Andy Wingo wrote: > Hi Ian, > > [re-adding the list; please keep the list CC'd on all guile-related > topics] > > On Fri 28 Jan 2011 22:37, Ian Hulin writes: > >> Are you going to fix the double extension bug for defaulted/cache

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Andy Wingo
Hi Ian, On Tue 19 Jul 2011 15:18, Ian Hulin writes: > It may boil down to a matter of taste, but I find double and triple > extensions on a filename intrinsically nasty. I've normally come across > them before on Windows systems where a filename such as thing.htm.exe > usually means there's mal

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Ian Hulin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue 19 Jul 2011 15:28:41 BST, Andy Wingo wrote: > Hi Ian, > > On Tue 19 Jul 2011 15:18, Ian Hulin writes: > >> It may boil down to a matter of taste, but I find double and >> triple extensions on a filename intrinsically nasty. I've normally >>

Guile V2.0 (include) procedure.

2011-07-19 Thread Ian Hulin
In another post Ludo mentioned an as yet undocumented (include) procedure. How does it differ from (load)? Could LilyPond add a stub for use with V1.8 (as we did for (module_export_all!) )? What's the calling interface? How does it interact with %load-path and %load-compiled-path? How is it af