Re: New read/eval Scheme syntax inconsistent in handling existing code

[David Kastrup]

Valentin Villenave <address@hidden> writes:

> On Fri, Dec 2, 2011 at 10:14 AM, David Kastrup <address@hidden> wrote:
>
>> Upgrade, rinse and repeat.  Up to now, your problems have exclusively
>> been unrelated to the nature of the patches, but rather because of
>> bugs slipping through the current regtest net that could be fixed
>> with few lines of code.
>
> I'm glad to read that. Indeed, the new staging branch compiles my
> scores (at least, the ones I've tested so far) with virtually no
> modification needed.

Good.

>> The use of "eval-string" does not just stick out like a sore thumb in
>> Lilypond.  It would also be considered really bad style in most
>> Scheme programs.
>
> I hear you. I used defmacro previously, but that wouldn't work any
> longer with the new define-music-function syntax (a "disruption" which
> I didn't nag you about, since I was able to cope with it by using
> hacks).

I don't see why defmacro should have ceased working, so it might be
worth revisiting the problems you experienced.

Maybe you are being too smart for your own good.

The work I am doing may partly be complex, but the aim is to make
Lilypond much more boring and predictable.  So if my changes drive you
to more awkward solutions, that is a sign that there is something wrong.
Either with my code, or your approach.  And I want to know about either,
so that I have a chance to fix code and/or documentation.

-- 
David Kastrup