char-generator Bradley Lucier (14 Jan 2024 17:45 UTC)
Re: char-generator Per Bothner (14 Jan 2024 17:59 UTC)
Re: char-generator Marc Nieper-Wißkirchen (14 Jan 2024 18:02 UTC)
Re: char-generator John Cowan (16 Jan 2024 02:28 UTC)
Re: char-generator Per Bothner (16 Jan 2024 06:10 UTC)
Re: char-generator Antero Mejr (16 Jan 2024 16:49 UTC)
Re: char-generator John Cowan (17 Jan 2024 02:49 UTC)
Re: char-generator Marc Nieper-Wißkirchen (14 Jan 2024 18:00 UTC)
Re: char-generator Bradley Lucier (14 Jan 2024 18:04 UTC)
Re: char-generator Marc Nieper-Wißkirchen (14 Jan 2024 18:06 UTC)
Re: char-generator Antero Mejr (15 Jan 2024 03:17 UTC)
Re: char-generator John Cowan (16 Jan 2024 01:40 UTC)

Re: char-generator Antero Mejr 15 Jan 2024 03:15 UTC

Marc Nieper-Wißkirchen <xxxxxx@gmail.com> writes:

> I agree.
>
> Bradley Lucier <xxxxxx@purdue.edu> schrieb am So., 14. Jan. 2024, 19:04:
>
>     On 1/14/24 12:59 PM, Marc Nieper-Wißkirchen wrote:
>     > If the implementation does not know any non-Unicode characters, calling
>     > integer->char on a non-Unicode code point is UB in R7RS.
>
>     OK.  But I think the sample implementation shouldn't have known
>     undefined behavior, let us say.

Updated sample implementation to only generate characters in the valid
Unicode ranges.