[erlang-questions] A proposal for Unicode variable and atom names in Erlang.

[Yurii Rashkovskii]

Rapsey,

Couldn't agree more. There are so many other more important issues that 
could have been addressed by the OTP team and contributors.

By the way, we just go this (lower and upper) implemented in Elixir, but it 
could be very well separated out of Elixir to be used by plain Erlang 
developers: http://coderwall.com/p/pehkba 

It compiles the necessary part of the unicode database right into the beam 
file, making it fairly efficient. Also, pending merge, I have a patch that 
makes upcase and downcase work with graphemes as opposed to codepoints 
(https://github.com/elixir-lang/elixir/pull/566), which we hopefully will 
merge in shortly.

Yurii.

On Monday, October 22, 2012 12:04:56 AM UTC-7, Rapsey wrote:
>
> On Mon, Oct 22, 2012 at 8:25 AM, Michael Richter <ttmri...@REDACTED<javascript:>
> > wrote:
>
>> On 22 October 2012 13:08, Yurii Rashkovskii <yra...@REDACTED<javascript:>
>> > wrote:
>>
>>> Please excuse my ignorance, but can you name a single good reason for 
>>> non-latin atoms and variable names? From my personal point of view, this is 
>>> a sure road to hell.
>>
>>
>> Because people frequently like to work in their own language instead of a 
>> foreign language they ill understand?
>>
>> Jesus!  How can so many smart people be so god-damned dumb over this 
>> issue?
>>
>
> I'm not from an english speaking country. I've worked for two development 
> companies and all had a strict english only rule on code and all 
> documentation. I am against this idea, simply because there are so many 
> more worthwhile things the OTP team could be spending time on. If we're 
> talking about unicode, a to_lower and to_upper function is a pretty big 
> missing feature.
>
>
> Sergej
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121022/383ebd16/attachment.htm>