Re: Rewriting the Translator definition framework

2016-04-23 Thread David Kastrup
Paul Morris writes: >> On Apr 22, 2016, at 8:07 AM, David Kastrup wrote: >> >> I am currently doing pitch 2 at first-class Scheme engravers and am >> sorely tempted to scratch the whole macro-based mess and do it via >> inheritance and templates. > > I can’t comment on the implementation questi

Re: Rewriting the Translator definition framework

2016-04-22 Thread Urs Liska
Am 23.04.2016 um 07:09 schrieb Paul Morris: > (Also, while I’m at it, your recent dotted list work, allowing "violin.1” > etc, is also really nice.) Oh, I seem to have missed this, but that's great. Finally we can write indexed parts/variables! Thanks for adding this, David. Best Urs

Re: Rewriting the Translator definition framework

2016-04-22 Thread Paul Morris
> On Apr 22, 2016, at 8:07 AM, David Kastrup wrote: > > I am currently doing pitch 2 at first-class Scheme engravers and am > sorely tempted to scratch the whole macro-based mess and do it via > inheritance and templates. I can’t comment on the implementation questions, but it will be great to h

Re: Rewriting the Translator definition framework

2016-04-22 Thread Werner LEMBERG
> I am currently doing pitch 2 at first-class Scheme engravers and am > sorely tempted to scratch the whole macro-based mess and do it via > inheritance and templates. Sounds OK to me. Thanks for working on this. Werner ___ lilypond-devel mailin

Re: Rewriting the Translator definition framework

2016-04-22 Thread David Kastrup
"Trevor Daniels" writes: > Not really an objection; just a thought. I can't comment on the > technicalities, and I've every confidence you can carry this through, > but I wonder about the position of existing compositions that include > custom C++ engravers in the old (i.e. current) style. If p

Re: Rewriting the Translator definition framework

2016-04-22 Thread Trevor Daniels
David Kastrup wrote Friday, April 22, 2016 1:07 PM > I am currently doing pitch 2 at first-class Scheme engravers and am > sorely tempted to scratch the whole macro-based mess and do it via > inheritance and templates. > > Now the sore point is that the basic type for which Scheme functions are

Re: Rewriting the Translator definition framework

2016-04-22 Thread Carl Sorensen
On 4/22/16 6:07 AM, "lilypond-devel on behalf of David Kastrup" wrote: > >Hi folks, > >I am currently doing pitch 2 at first-class Scheme engravers and am >sorely tempted to scratch the whole macro-based mess and do it via >inheritance and templates. > >Now the sore point is that the basic type f

Rewriting the Translator definition framework

2016-04-22 Thread David Kastrup
Hi folks, I am currently doing pitch 2 at first-class Scheme engravers and am sorely tempted to scratch the whole macro-based mess and do it via inheritance and templates. Now the sore point is that the basic type for which Scheme functions are defined is that of a Translator. And Engravers and