On Mon, May 25, 2009 at 10:39 AM, 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,,, > I assume besides the differences in 32/64 bit, there are differences with debug and non-debug fasl files (well in my case with IronScheme, the fasl files grow considerably with debugging info embedded, not sure what the case is with Ikarus). Cheers leppie -- http://codeplex.com/IronScheme http://xacc.wordpress.com
