Re:Having a Go - first time experience with Golang
by mseepgood on Monday July 09, 2012 @11:09AM
(#4218515)
Writing non-English identifiers in a programming language that is based on English keywords seems wrong to me anyway. I'm not an English native speaker myself, but I accept that the international language of programming and source code is English.
Re:Having a Go - first time experience with Golang
by kibwen on Monday July 09, 2012 @11:38AM
(#4218659)
English is my only natural language, so I don't feel qualified to comment on whether or not this is attitude is acceptable in circles where English is not the native tongue. But from a language design standpoint, why even allow Unicode identifiers if you're going to foist ASCII on everyone anyway?
EDIT: Actually, I suppose Unicode-awareness means that they'd be foisting Unicode Category Lu[1] on everyone rather than simply ASCII.
[1] http://www.fileformat.info/info/unicode/category/Lu/list.htm
Re:Having a Go - first time experience with Golang
by masklinn on Monday July 09, 2012 @11:43AM
(#4218680)
> Writing non-English identifiers in a programming language that is based on English keywords seems wrong to me anyway.
Then it should not be allowed at all.
Language users will find a way though, they can just write phonetically.
I knew that Go was both case-significant and Unicode-aware, but I had assumed (perhaps incorrectly) that they'd have some mechanism to export identifiers written in scripts that don't have a case distinction. Can anyone verify this? Or do they really expect e.g. Japanese programmers to write identifiers like `A緑` instead of `緑`?