Re: misleading message and exit code when "program too old"

2015-11-11 Thread Urs Liska
Am 11.11.2015 um 22:16 schrieb tisimst: > The \version statement mostly serves two purposes: > > 1. Remind you what compiler version you initially coded it for > 2. Makes it possible for convert-ly to upgrade it to newer versions when > desired However (and including Simon's comments) I've always

Re: Re: misleading message and exit code when "program too old"

2015-11-11 Thread tisimst
Johannes, On Wed, Nov 11, 2015 at 1:54 PM, Johannes Waldmann [via Lilypond] < ml-node+s1069038n183442...@n5.nabble.com> wrote: > Hi, > > it's really not a big deal since I have a work-around > (ignore the exit code in my Makefile) > > I understand that specifying and checking the version > can be

Re: Re: misleading message and exit code when "program too old"

2015-11-11 Thread Johannes Waldmann
Hi, it's really not a big deal since I have a work-around (ignore the exit code in my Makefile) I understand that specifying and checking the version can be useful. I am just saying that the actual message and behaviour (exit code) is surprising. >From the compilers I know (say, gcc) there's a c

Re: misleading message and exit code when "program too old"

2015-11-11 Thread Malte Meyn
Am 11.11.2015 um 14:19 schrieb Johannes Waldmann: Hi. I am getting this: Parsing... error: program too old: 2.18.2 (file requires: 2.19.0) but apparently it's not an error, Yes, it is because the file states to need version 2.19.0 and you cannot be sure that 2.18.2 will be sufficient. since