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

No valid literal format for unprintable Strings #184

Open
blairmcg opened this issue Apr 4, 2016 · 1 comment
Open

No valid literal format for unprintable Strings #184

blairmcg opened this issue Apr 4, 2016 · 1 comment
Assignees

Comments

@blairmcg
Copy link
Contributor

blairmcg commented Apr 4, 2016

Smalltalk doesn't have an escaped literal form for characters that don't have a standard glyph, e.g. whitespace, null, escape. Most languages provide an escaping mechanism to allow these to be specified as literals using an alternate form, e.g. '\n' for '\x0D' for linefeed. This c-style escaping has been adopted into many languages, and although it doesn't use the traditional Smalltalk form for expressing hex, it is much more concise and generally understood.
The ability to specify characters with arbitrary code points will become even more important when Unicode is supported.

@blairmcg
Copy link
Contributor Author

blairmcg commented Jun 2, 2016

Done for Characters

@blairmcg blairmcg self-assigned this Jun 2, 2016
@blairmcg blairmcg changed the title No valid literal format for unprintable Characters and Strings No valid literal format for unprintable ~~Characters and~~ Strings Dec 21, 2016
@blairmcg blairmcg changed the title No valid literal format for unprintable ~~Characters and~~ Strings No valid literal format for unprintable Strings Dec 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant