Maxime Devos writes:
> Jean Abou Samra schreef op wo 09-03-2022 om 00:31 [+0100]:
>> In summary, the less Guile optimizes, the faster LilyPond runs. Is that
>> something expected?
>
> I don't think so, but I don't have a clue how this happens ...
Do I understand it correctly that Lilypond has lo
> Le 9 mars 2022 à 08:53, "Dr. Arne Babenhauserheide" a écrit
> :
>
>
> Maxime Devos writes:
>> Jean Abou Samra schreef op wo 09-03-2022 om 00:31 [+0100]:
>>> In summary, the less Guile optimizes, the faster LilyPond runs. Is that
>>> something expected?
>>
>> I don't think so, but I don't
Jean Abou Samra writes:
>>> There is also a felicitous feedback effect in that because the
>>> baseline compiler is much smaller than the CPS compiler, it takes less
>>> time to macro-expand —
>>> https://wingolog.org/archives/2020/06/03/a-baseline-compiler-for-guile
>
> As far as I understand,
Vijay Marupudi schreef op vr 21-01-2022 om 20:21 [-0500]:
> +SCM_DEFINE (scm_utf16_range_to_string, "utf16->string",
> + 1, 3, 0,
> + (SCM utf, SCM endianness, SCM start, SCM end),
> + "Return a newly allocate string that contains from the
> UTF-8-"
> + "
Vijay Marupudi schreef op vr 21-01-2022 om 20:21 [-0500]:
> +SCM_DEFINE (scm_utf8_range_to_string, "utf8->string",
> + 1, 2, 0,
> + (SCM utf, SCM start, SCM end),
> + "Return a newly allocate string that contains from the
> UTF-8-"
> + "encoded contents o
Vijay Marupudi schreef op vr 21-01-2022 om 20:21 [-0500]:
> +SCM_DEFINE (scm_utf8_range_to_string, "utf8->string",
> + 1, 2, 0,
> + (SCM utf, SCM start, SCM end),
> + "Return a newly allocate string that contains from the
> UTF-8-"
> + "encoded contents o
Maxime Devos schreef op wo 09-03-2022 om 14:24 [+0100]:
> This is incorrect, since the nul character is encoded even though
> UTF-
> proper does not allow encoding the nul character -- UTF-8 with an
> encoding of the nul character is sometimes called ‘modified UTF-8’.
That's not quite correct, see
Maxime Devos schreef op wo 09-03-2022 om 14:27 [+0100]:
> That's not quite correct, seems like Guile uses another encoding, but
> still.
Nevermind, seems like a misinterpreded a comment and #vu8(97 0 98) is
valid UTF-8 after all, it's just not possible to encode it as a zero-
terminated string.
Maxime Devos writes:
> Nevermind, seems like a misinterpreded a comment and #vu8(97 0 98) is
> valid UTF-8 after all, it's just not possible to encode it as a zero-
> terminated string.
Thanks for the catch on the typo in the docstrings. I've attached the
updated versions of the patches that fix
