Nala Ginrut writes:
> I try to port sweet-expression to newest Guile. Fortunately, the
> author wrote a compatible version for old Guile in 2008. So I just try
> to rewrite part of it for some obvious reasons. It woks fine now.
>
> Though some guys doesn't like sweet-expression at all (OK, they'r
Nala Ginrut writes:
> I try to port sweet-expression to newest Guile. Fortunately, the
> author wrote a compatible version for old Guile in 2008. So I just try
> to rewrite part of it for some obvious reasons. It woks fine now.
>
> Though some guys doesn't like sweet-expression at all (OK, they'r
sorry for stupid typo:
s/Python of C/Python or C
Regards
I try to port sweet-expression to newest Guile. Fortunately, the author
wrote a compatible version for old Guile in 2008. So I just try to rewrite
part of it for some obvious reasons. It woks fine now.
Though some guys doesn't like sweet-expression at all (OK, they're real
Lispers! But me too ;-)).
Hi Andy, thanks for the quick response! :)
Andy Wingo writes:
> On Mon 05 Mar 2012 18:17, Mark H Weaver writes:
>
>> It makes 'gensym' about 4.7 times faster on my Yeeloong. Gensyms are
>> not given names or even numbers until they are asked for their names or
>> hash values (for 'equal?' hash
David Kastrup writes:
> Mark H Weaver writes:
>
>> Excellent! As long as you load everything in the right order, such that
>> macros are defined before they are used, I don't see why there should be
>> any other problems related to macros and compilation.
>
> Because the individual files are no
Mark H Weaver writes:
> David Kastrup writes:
>
>> Mark H Weaver writes:
>>
>>> David Kastrup writes:
>>>
with the stable release 2.16 of LilyPond looming around the corner, it
will become imminent soon to think about supporting Guile 2.0.
Previous attempts have mostly expl
Hi Mark,
A quick reaction to your summary; I'll look at the patches shortly.
On Mon 05 Mar 2012 18:17, Mark H Weaver writes:
> Here's an implementation of the efficient gensym hack for stable-2.0.
Excellent!
> It makes 'gensym' about 4.7 times faster on my Yeeloong. Gensyms are
> not given n
David Kastrup writes:
> Mark H Weaver writes:
>
>> David Kastrup writes:
>>
>>> with the stable release 2.16 of LilyPond looming around the corner, it
>>> will become imminent soon to think about supporting Guile 2.0.
>>>
>>> Previous attempts have mostly exploded around the problem that we hav
Hello all,
Here's an implementation of the efficient gensym hack for stable-2.0.
It makes 'gensym' about 4.7 times faster on my Yeeloong. Gensyms are
not given names or even numbers until they are asked for their names or
hash values (for 'equal?' hash tables only).
The first patch adds an optim
Mark H Weaver writes:
> David Kastrup writes:
>
>> with the stable release 2.16 of LilyPond looming around the corner, it
>> will become imminent soon to think about supporting Guile 2.0.
>>
>> Previous attempts have mostly exploded around the problem that we have
>> something like
>>
>> (for-ea
David Kastrup writes:
> with the stable release 2.16 of LilyPond looming around the corner, it
> will become imminent soon to think about supporting Guile 2.0.
>
> Previous attempts have mostly exploded around the problem that we have
> something like
>
> (for-each ly:load init-scheme-files)
>
>
Hi,
with the stable release 2.16 of LilyPond looming around the corner, it
will become imminent soon to think about supporting Guile 2.0.
Previous attempts have mostly exploded around the problem that we have
something like
(for-each ly:load init-scheme-files)
in our lily.scm file, and the aut
13 matches
Mail list logo
