Re: Premature evaluation.

[David Kastrup]

Carl Sorensen <address@hidden> writes:

> On 4/15/10 3:00 AM, "David Kastrup" <address@hidden> wrote:
>
>> Something like that.  Splitting scanning and evaluating into two should
>> ensure that the evaluation happens not at a time when the parsing of
>> preceding constructs has not yet properly completed.
>
> I'm sure that a patch would be gratefully accepted.  This is clearly
> undesirable behavior.

Here is the problem: #... can not just evaluate to SCM_TOKEN, but also
to all sorts of xxx_IDENTIFIER.  With my approach, just SCM_TOKEN would
come out unless one takes additional precautions.

I am trying to figure out how to deal with this special case, but I
actually am unable to figure out just what input might produce
xxx_IDENTIFIER.

Things like

xxx = { c d e f }

{ #xxx }

or

{ #'xxx }

are not making Lilypond happy.

Can somebody give me an actual example for the provided functionality?

-- 
David Kastrup