Re: libc.lsh

Some definitions in libc.lsh might be problematic because
memory management had changed (malloc & free), and most
others were redundant. @ and @@ as they were defined in
libc/constants was unecessary, I thought (why limit your
namespace, especially if there are better ways ?). 
For both situations there are alternatives--just use
defconstant and #. for read-time evaluation, as in
common lisp.

I removed those files so that it is clear which files I
still need to update and what to look for.

Ralf



On Fri, 31 Jul 2009, Yann LeCun wrote:

> Hi Ralf,
>
> Any good reason for not removing libc.lsh and constants.lsh
> from Lush2 in lsh/libc?
>
> SDL and a whole bunch of other packages use them.
>
> Is there another to do the same thing on Lush2?
>
>  -- Yann
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Lush-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/lush-devel
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july