- **Patch**: countdown --> needs_work
- **Comment**:
there is something odd here; James says it passes make check, but I get
lilypond-g18]$ ./out/bin/lilypond input/regression/display-lily-tests.ly
GNU LilyPond 2.21.0
Processing `input/regression/display-lily-tests.ly'
Parsing...
<string>:1:15: fatal error: GUILE signaled an error for the expression
beginning here
c4\bendAfter #
3
---
** [issues:#5741] Parse inline scheme using per-expression port**
**Status:** Started
**Created:** Fri Feb 07, 2020 02:52 PM UTC by Han-Wen Nienhuys
**Last Updated:** Wed Feb 12, 2020 12:05 PM UTC
**Owner:** Han-Wen Nienhuys
Introduces a throw-away string port, Overlay_string_port, which makes
a port out of a random section of a C string. It does not own the
string, so there is no overhead in creating and discarding the ports
during parse time.
For GUILE v2, Overlay_string_port uses UTF-8 encoding, so UTF-8
encoded string constants within the Scheme constants are interpreted
as Unicode correctly.
This obviates the string port that Source_file carries along.
This commit fixes a problem with GUILE 2.2.6, where LilyPond
calculates offsets in the source file as bytes, while GUILE interprets
the source file as UTF-8 encoded Unicode. As a result, files with
Unicode before embedded scheme break completely.
https://codereview.appspot.com/557330043
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list._______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
