Re: Context.Grob considered as symbol list

[Werner LEMBERG]

>> On the other hand: Wouldn't it be possible to make LilyPond simply
>> walk over all possible combinations to find out whether, say,
>>
>>   foo.bar
>>
>> is a context followed by a property, or a property followed by a
>> sub-property, etc.?
>
> Technically impossible.  At the time an \override is parsed, the
> valid set of contexts has not been established.

OK.  And the interpretation of the just parsed data (this is, checking
the validity of contexts, properties, etc.) can't be delayed, right?

> LilyPond's parser is written with Bison, a standard parser generator
> normally used for writing that part of a compiler that would deal
> with syntax.  LilyPond's free-form language stretches the
> capabilities of Bison beyond what it has been designed for.

Interesting.  My knowledge here is very limited.

> So let's just assume I have heard of compilers.  Give me a bit of
> credit here.

I don't doubt your capabilities.  I only refer to error messages which
I've seen while working with C++ code.


    Werner