Re: Weird issue with dotted-list-notation

[David Kastrup]

Urs Liska <address@hidden> writes:

> Am 23.03.2015 um 17:30 schrieb David Kastrup:

>> Ok thanks.  If you want to have more of a go at reproducing the problem,
>> it's clearly also related to the use of \include, possibly in connection
>> with some
>> #(ly:parser-[whatever] "\\include ...")
>> call.  It may be that the combination of
>>
>> \callacceptingsymbollist ... xxx.yyy.zzz
>> \somevariantofinclude ...
>>
>> is at fault when the lookahead scope of the symbol list meshes with the
>> \include.
>
> OK.
> The weird thing is that I can put any debug (display) or ly:message I
> want all the way from the signature down to the \include, and
> everything seems completely right, the output (i.e the state of all
> the variables in between) is always the expected.

Why would that be weird?  This is a parse error, and the inner state of
the parser is not something you'd see in a user-accessible variable.

> So as of now I can only say people should use proper Scheme lists as
> argument or ensure there's a Scheme expression after the function call
> (and not a LilyPond one).

Probably anything else before an \include will do as well.

> Do you think there's a chance to find the issue in my code or in the
> parser or do I have to live with that?

Why do you think I told you what elements your minimal example should
likely have in order to trigger the problem in a better debuggable and
less complex session?  We need something smaller for a proper issue
report.  It may be that you need two files to reproduce the problem as
it seems to be related to \include, but the files probably can be quite
small.

-- 
David Kastrup