Re: Some wild considerations and a question

2020-10-20 Thread Jonas Hahnfeld
Am Dienstag, den 20.10.2020, 19:26 +0200 schrieb David Kastrup: > Jonas Hahnfeld writes: > > > Am Dienstag, den 20.10.2020, 18:26 +0200 schrieb David Kastrup: > > > Jonas Hahnfeld writes: > > > > > > > I don't want to digress into this topic right now (P.S. the reply got > > > > longer than I i

Re: Some wild considerations and a question

2020-10-20 Thread Karlin High
On 10/20/2020 12:26 PM, David Kastrup wrote: Jonas Hahnfeld writes: For my own reading pleasure, do you have links where this was discussed? That would not be in the GUB repo but in GNU's internal discussion lists. There were a few sort-of discussions/attempts on the lilypond-devel list to c

Re: Some wild considerations and a question

2020-10-20 Thread David Kastrup
Jonas Hahnfeld writes: > Am Dienstag, den 20.10.2020, 18:26 +0200 schrieb David Kastrup: >> Jonas Hahnfeld writes: >> >> > I don't want to digress into this topic right now (P.S. the reply got >> > longer than I initially anticipated), but the scripts have a much >> > narrower focus: they mostl

Re: Some wild considerations and a question

2020-10-20 Thread Jonas Hahnfeld
Am Dienstag, den 20.10.2020, 18:26 +0200 schrieb David Kastrup: > Jonas Hahnfeld writes: > > > I don't want to digress into this topic right now (P.S. the reply got > > longer than I initially anticipated), but the scripts have a much > > narrower focus: they mostly compile native binaries (excep

Re: Some wild considerations and a question

2020-10-20 Thread David Kastrup
Jonas Hahnfeld writes: > I don't want to digress into this topic right now (P.S. the reply got > longer than I initially anticipated), but the scripts have a much > narrower focus: they mostly compile native binaries (except for > Windows via mingw) instead of cross-compiling for all targets. In

Re: Some wild considerations and a question

2020-10-20 Thread Jonas Hahnfeld
Let me address the points about GUB: Am Dienstag, den 20.10.2020, 11:03 +0200 schrieb Jean Abou Samra: > > > - rely only on C++, flex, bison and the extension language. > > >    Eliminating the need for GUB and Python would greatly simplify > > >    porting LilyPond to various environments, includ

Re: Some wild considerations and a question

2020-10-20 Thread Jean Abou Samra
Greetings everybody, - rely only on C++, flex, bison and the extension language. Eliminating the need for GUB and Python would greatly simplify porting LilyPond to various environments, including web sites, phones and tablets. GUB will be history soon, thanks to the work mainly of Jo

Re: Some wild considerations and a question

2020-10-19 Thread David Kastrup
Jacques Menu writes: > Hello folks, > > Sorry, this message is rather long… > > > I’ve been wondering what design decisions would be made, should > someone start a project like LilyPond today, with the years-long > experience we have behind us in this field. > > LilyPond can be characterized the

Re: Some wild considerations and a question

2020-10-19 Thread Thomas Morley
Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu : > We often have to add things such as short skips and cadenzas to avoid having > so-called events at the exact same time moment in the score. > This is illustrated by \HiddenMeasureAndBarLine in the attached file: > commenting its use out

Re: Some wild considerations and a question

2020-10-19 Thread Thomas Morley
About issue 34 Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu : > LilyPond can be characterized the following way, please excuse any important > omission or error: > - the implementation is one-pass, meaning that the work done when > handling a file goes straight from the char

Re: Some wild considerations and a question

2020-10-19 Thread Thomas Morley
Hi Jacques, I split my replies to address different aspects separately. This one about scheme/guile Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu : > Some aspects of the current state of the Lily implementation are a bit > saddening: > - Scheme is not easy to read nor write f

Re: Some wild considerations and a question

2020-10-19 Thread Martín Rincón Botero
Just my two cents to this comment: > switch to another, easier to read and write extension language. Someone > suggested Lua, for example, which would be a good candidate it seems I don’t know about Lua, but as a non-programmer, I spent many days getting in grips with Scheme. The result were ver

Re: Some wild considerations and a question

2020-10-19 Thread Andrew Bernard
Are you talking about reimplementing LilyPond from scratch? I'm happy with Scheme, as a programmer. It's the Guile implementation that causes the performance issue with Guile 2, not the Scheme languages. Perhaps it's just that with advanced tools one requires advanced knowledge. As with anythi

Re: Some wild considerations and a question

2020-10-18 Thread Werner LEMBERG
Hello Jacques, > There have been very interesting discussions about all this at the > Salzburg conference last January, which lead me to dream of things > being done another way in an ideal world: [...] > > - switch to another, easier to read and write extension language. > Someone suggested

Some wild considerations and a question

2020-10-18 Thread Jacques Menu
Hello folks, Sorry, this message is rather long… I’ve been wondering what design decisions would be made, should someone start a project like LilyPond today, with the years-long experience we have behind us in this field. LilyPond can be characterized the following way, please excuse any impo