Urs Liska <u...@openlilylib.org> writes:
> Am 29.06.2016 um 17:12 schrieb David Kastrup:
>> Johan Vromans <jvrom...@squirrel.nl> writes:
>>>
>>> Except that in C #include is significantly different from the rest
>>> of the C syntax. #-lines are all different and independent of
>>> C-lines and syntax.
>>
>> The same with LilyPond. You can put \include in the midst of any
>> LilyPond construct without bothering about nesting. Try
>>
>> a.ly:
>>
>> \score { a_\include "b.ily" } }
>>
>> b.ily:
>>
>> 3^\markup { hi
>>
>> This is not the mark of a construct working in a syntactical context.
>>
>
> That's not what Johan is talking about. What he refers to is that the
> C #include syntax *looks* completely different from regular C/C++
> code, so nobody will mistake it for a regular function call or
> whatever.
>
> But \include *looks* like it's working the same as \shape.
Where do you want to go from there?
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
