Werner LEMBERG <w...@gnu.org> writes: >> [...] >> >> This is a quantum leap backwards in making LilyPond and Scheme >> expressions and variables and functions and arguments in the parser >> work and combine in a predictable manner. >> >> I am working hard on stopping the Scheme layer from being something >> entirely different and interacting in unpredictable ways with >> LilyPond depending on where variables and function arguments start >> and end. >> >> I really don't get why people are keen on destroying all progress we >> have made regarding a straightforward relation between Scheme and >> LilyPond. > > David, please relax. I've typeset hundreds of pages with lilypond, > including complicated piano and organ music; I don't lightly suggest > syntactic stuff just to annoy you.
We are getting most certainly nowhere if people don't even bother understanding the technical points of my replies. They get no followup, and the next proposal coming up is not any more suitable for pretty much the same reasons. > Graham's and my suggestions are very restrictive, and we are just > playing around with possible syntax forms. How about considering how they are supposed to translate to and from Scheme? > It would be tremendously helpful if you can show possible syntax > *alternatives* instead of just pretending to be a naysayer. I've posted actual working definitions for that purpose. They would definitely simplify the kind of entry you are asking for. However, nobody can be interested in them since they don't necessitate parser changes. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel