Re: mixing lush with clush
Yann LeCun <[email protected]> Thu, 16 Mar 2006 20:44:52 -0500
| Newsgroups | gmane.lisp.lush.devel |
|---|---|
| Organization | Courant Institute, NYU |
| Message-ID | <[email protected]> |
Actually, the best fix is probably to extend (or rewrite) the compiler so that everything can be compiled. This means adding a garbage collector for compiled code, among other things. -- Yann On Thursday 16 March 2006 08:19 pm, Yury Sulsky wrote: > Hi all, > > I was thinking- I really like Lush proper, but CLush is basically just > prefix C with a better macro system. The problem is that you can't > have code paths that include interpreted portions, so you have to > decide a priori how much of your program will be compiled. > > It seems like the fix for this is to improve the C-->LISP interface so > that calls to non-compilable code can be automatically marshalled by > the compiler (something you can already do by hand when writing inline > C). > > Any comments/suggestions where to get started? > > Thanks > Yury > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live > webcast and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd________________________________________ >_______ Lush-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lush-devel ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642