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

[Valentin Villenave]

On Fri, Nov 25, 2011 at 6:18 PM, David Kastrup <address@hidden> wrote:
> Valentin, any more news of bad effects on your scores?  Apart from the
> bug that should now be fixed?

OK, I've now had a chance to test the staging code, it's certainly an
improvement!

... Aand I'm blocked by another bug (or unwanted behavior) that
affects nested levels of string evaluations.

I have yet to track down the exact problem, but here's an example of
the quirks I used to rely upon:


myvar = { b'4 }

$(eval-string "(define-public myvar #{ a'2 #} )" )

\new Staff \myvar


(Granted, this wouldn't have worked with previous versions either. But
the mechanism is the same.)

I'll let you know if I can narrow it down to a working sample.

Cheers,
Valentin.