Or were you thinking that if they are in ~/.ikarus we can just delete them etc. manually? Since we know where they are and we have write access... that might be simplest.
btw what does fasl stand for, if anything? On Mon, May 25, 2009 at 6:58 PM, Ramana Kumar <[email protected]> wrote: > I like the idea of letting ikarus manage fasl files (which I presume > is what you mean by putting them all in ~/.ikarus/something). > > Then you should probably provide switches and/or procedures for > removing fasl files, or forcing an update when compiling. > > Is there any way to compile libraries without a script? > > On Mon, May 25, 2009 at 6:39 PM, Abdulaziz Ghuloum <[email protected]> wrote: >> Greetings, >> >> I need some feedback. >> >> Fasl files (i.e., precompiled, binary library files) currently >> go into the same place where the library is. E.g., compiling >> the library (foo bar) which is located in <path>/foo/bar.sls >> produces <path>/foo/bar.sls.ikarus-fasl. This has some pros >> (it's a simple mapping; you can nuke a library with its fasl >> files altogether; users can share libraries and fasl files; >> etc.) but it also has some disadvantages (you may not have >> write access to the directory; you cannot mix and match 32- >> and 64-bit fasl files for the same library; upgrading ikarus >> breaks precompiled libraries; it pollutes the library path >> with junk files; etc.). >> >> Should this change? And what to? >> >> I'm inclined towards the ypsilon model (put fasl files in a >> $HOME/.ikarus/precompiled directory). >> >> Any comments, suggestions, or objections? Please speak up. >> >> Aziz,,, >> >
