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

[David Kastrup]

David Kastrup <address@hidden> writes:

> Valentin Villenave <address@hidden> writes:
>
>> On Mon, Nov 21, 2011 at 7:39 PM, David Kastrup <address@hidden> wrote:
>>
>>> A bug that made it through the reviews, nothing inherently bad about
>>> the design.  Thanks for the test example, by the way.
>>
>> Yes, it looks probably a bit far-fetched but said bug did break all of
>> my scores! (Hence the disruption thing.)
>
> Could you recheck with current staging?  It would appear that you are in
> possession of the most comprehensive test suite available...

BTW, it would also be good to hear if #(ly:parser-parse-string ...) goes
haywire often enough in existing use to warrant a general
convertrules.py conversion rule to $(ly:parser-parse-string ...).  And
if the latter would actually help.

-- 
David Kastrup