Ian Hulin <i...@hulin.org.uk> writes:
> This is forwarded from the Guile bug list. Bug-squad please create a
> LilyPond issue for this - we need to change our code:
>
> Files affected appear (according to git grep) to be:
> lily/mensural-ligature.cc
> lily/system.cc
> scm/c++.scm
> scm/define-event-classes.scm
> scm/music-functions.scm
I am responsible for most of those, and will fix them. No issue
required here.
For my defense, neither *unspecified* nor unspecified? are documented in
the Guile-1.8 manual though working at the prompt. So while the 1.8
branch is still maintained, you should report this as a documentation
bug. And after all, it _does_ affect upwards-compatibility.
And in fact, the only _documented_ way of generating this value from
Scheme is
-- syntax: begin expr1 expr2 ...
The expression(s) are evaluated in left-to-right order and the
value of the last expression is returned as the value of the
`begin'-expression. This expression type is used when the
expressions before the last one are evaluated for their side
effects.
Guile also allows the expression `(begin)', a `begin' with no
sub-expressions. Such an expression returns the `unspecified'
value.
So if they want people to have a reasonably working upgrade path from
1.8, they better make sure that 1.8 documents the things they want to
be seeing in code.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
