Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation-defined character set #15

Open
ruv opened this issue Nov 7, 2024 · 0 comments
Open

Implementation-defined character set #15

ruv opened this issue Nov 7, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@ruv
Copy link
Collaborator

ruv commented Nov 7, 2024

Rationale/clarification for implementation-defined character set is wanted:

This draft never fails to amaze in what it won't commit to. 3.1.2.2 is the first time implementation-defined character set is mentioned (out of 6 references in the document), yet its not discussed before that nor any rationale. They state ASCII is used, of which 0..31 are well defined controls including DEL, so how / when / why would you have an implementation-defined character set - maybe some rationale for 3.1.2, 3.1.2.1, 3.1.2.2 might help, for example:

   An `implementation-defined character set` can be any character set where 7-bit ASCII is a proper subset.
   For example UTF-8 encoding, Extended ASCII, Latin1 to name a few.

Originally posted by @SirWumpus in ForthHub/discussion#121 (reply in thread)

@ruv ruv added the enhancement New feature or request label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant