- **labels**: --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->
- **Comment**:
~~~
Parse inline scheme using per-expression port staging
author Han-Wen Nienhuys <han...@lilypond.org>
Tue, 18 Feb 2020 08:40:00 +0000 (09:40 +0100)
committer Han-Wen Nienhuys <han...@lilypond.org>
Sat, 22 Feb 2020 10:35:37 +0000 (11:35 +0100)
commit 483292eb80da0869d22cd773eb480c662a499e89
~~~
---
** [issues:#5741] Parse inline scheme using per-expression port**
**Status:** Fixed
**Labels:** Fixed_2_21_0
**Created:** Fri Feb 07, 2020 02:52 PM UTC by Han-Wen Nienhuys
**Last Updated:** Sat Feb 22, 2020 09:59 AM 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 testlilyissues-a...@lists.sourceforge.net 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
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
