A run of the regression tests at "5f4cf7bd38 - Parse inline scheme
using per-expression port" shows the following issues compared to
GUILE 1.8
changed interleaving of error and progress messages.
floating point rounding differences.
an encoding error in song-basic-nonenglish.ly
As of a19aed1 "GUILE2: Scale GC heap with the number of smobs",
performance for large scores with GUILE 2.2 is similar to GUILE 1.8.
For small scores, a 1.5 sec extra delay (due to byte-code compilation
of .scm files) remains, but this does not warrant the "highly
experimental" monniker.
guile-config after guile-config2.2
https://codereview.appspot.com/569390043
pkg-config
https://codereview.appspot.com/569390043
stats
https://codereview.appspot.com/569390043
jonas' comments
https://codereview.appspot.com/569390043
Diff:
Passes make, make check and a full make doc.
Patch on countdown for Feb 24th
Patch counted down - please push
I think we need to redial or augment some of this patch since it will leave even experienced developers with an unexpected result.
If I now do
GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config ./configure
on my system the slow and crash-prone Guile-2.2 will be used. I would have been notified of that because the configuration would have failed because of a missing --with-guilev2 option, but this option is no longer necessary. So my explicit choice of Guile-1.8, made in the previously supported manner, will get silently ignored.
That is not good. I think that if GUILE_CONFIG is given, it should be heeded rather than ignored. Also if PKG_CONFIG_PATH is given in the environment, it should be recorded so that
./config.status --recheck
will not forget about it again.
We have dropped too many safety nets for making sure that our configure does what is expected of it.