Re: Let the parser interpret alist variables (issue 290560043 by d...@gnu.org)

2016-03-14 Thread dak
On 2016/03/13 23:39:29, thomasmorley651 wrote: Even from description the consequences are not clear to me. Can you give a little verbose example? Basically, you can now use x.y for defining and \x.y for using a variable like you could previously use x_y and \x_y but the value is really stored

Re: Let the parser interpret alist variables (issue 290560043 by d...@gnu.org)

2016-03-14 Thread dak
Reviewers: thomasmorley651, lemzwerg, https://codereview.appspot.com/290560043/diff/1/lily/nested-property.cc File lily/nested-property.cc (right): https://codereview.appspot.com/290560043/diff/1/lily/nested-property.cc#newcode137 lily/nested-property.cc:137: for (;scm_is_pair (prop_path);

Re: Let the parser interpret alist variables (issue 290560043 by d...@gnu.org)

2016-03-14 Thread lemzwerg
LGTM. https://codereview.appspot.com/290560043/diff/1/lily/nested-property.cc File lily/nested-property.cc (right): https://codereview.appspot.com/290560043/diff/1/lily/nested-property.cc#newcode137 lily/nested-property.cc:137: for (;scm_is_pair (prop_path); prop_path = scm_cdr (prop_path))

Let the parser interpret alist variables (issue 290560043 by d...@gnu.org)

2016-03-13 Thread thomasmorley65
Even from description the consequences are not clear to me. Can you give a little verbose example? https://codereview.appspot.com/290560043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel