[erlang-questions] Erlang basic doubts about String, message passing and context switching overhead

Oliver Korpilla <>
Sat Jan 14 21:25:09 CET 2017


Hello, Ilya.
 
Erlang community can address all its own problems if it wants. You can do so if you have the means and if you want. 
 
elixir developers made their own choices and I use elixir every day as my preferred BEAM language, not Erlang. I come here for BEAM and OTP knowledge.
 
Besides, if you really want, you can write part of your application in elixir, benefit from its feature set, and code the rest in Erlang. BEAM and rebar support that.
 
Which means: Everybody in BEAM community can _already_ use. 
 
Oliver
 

Gesendet: Samstag, 14. Januar 2017 um 21:19 Uhr
Von: "Ilya Khaprov" <>
An: "Michał Muskała" <>, "Oliver Korpilla" <>
Cc: "Erlang Questions" <>
Betreff: Re: [erlang-questions] Erlang basic doubts about String, message passing and context switching overhead

 

>> Elixir takes the files directly from unicode distribution, and uses macros to compile them down into regular functions.
 
Code generation. Can be done without macros, just generating Erlang files. So everyone in BEAM community can use. That is my point.
 
------------------------------------------------------------

From: Michał Muskała <>
Sent: Saturday, January 14, 2017 22:56
To: Oliver Korpilla; Ilya Khaprov
Cc: Erlang Questions
Subject: RE: [erlang-questions] Erlang basic doubts about String, message passing and context switching overhead
 

On 14 Jan 2017, 17:00 +0100, Ilya Khaprov <>, wrote:
 

>> Given that both Erlang and elixir are implemented on top of BEAM, the wheel might not need reinventing?
 
Why Elixir implements Unicode in Elixir? You have to rewrite it anyway. 

 
Elixir takes the files directly from unicode distribution, and uses macros to compile them down into regular functions. BEAM is wonderful at optimising bitstring pattern matching, so the resulting code is quite efficient and does not need NIFs. The whole implementation is also about 500 LoC https://github.com/elixir-lang/elixir/blob/master/lib/elixir/unicode/unicode.ex, so it's not a monstrosity and the code is quite readable.

[https://github.com/elixir-lang/elixir/blob/master/lib/elixir/unicode/unicode.ex]
 
elixir/unicode.ex at master · elixir-lang/elixir · GitHub[https://github.com/elixir-lang/elixir/blob/master/lib/elixir/unicode/unicode.ex]
github.com
elixir - Elixir is a dynamic, functional language designed for building scalable and maintainable applications 
 
On 14 Jan 2017, 16:53 +0100, Oliver Korpilla <>, wrote:Could the Unicode support in elixir serve as a starting point?

https://hexdocs.pm/elixir/1.3.3/String.html#content

String.upcase/1 and String.downcase/1 seem to be Unicode-aware. And a lot of effort seems have gone in scenarios like this:

"For example, the codepoint “é” is two bytes:

iex> byte_size("é")
2"

Given that both Erlang and elixir are implemented on top of BEAM, the wheel might not need reinventing? I know engineers and programmers love inventing stuff, and this discussion seems to point in that direction, but...
 
All the functions in the Elixir's String module are unicode aware. There are functions for unicode normalisation (both nfd and nfc) and checking equivalency (e.g. "é" can be a single code point, or two code points - the letter "e" and the combining diacritic acute). String.length/1 works in terms of unicode graphemes (multiple codepoints can compose into a single grapheme):
 
iex> String.length("é")
1
 
On 14 Jan 2017, 16:30 +0100, Benoit Chesneau <>, wrote:
someone has to write a good binding (non blocking) of icu :) I think it would be easier than reinventing the wheel. i18n [1] was a good start but looks abandoned these days. Also I disliked the load of resources at startup in ETS: https://github.com/erlang-unicode/i18n[https://github.com/erlang-unicode/i18n]

[https://github.com/erlang-unicode/i18n]
 
GitHub - erlang-unicode/i18n: icu nif: international ...[https://github.com/erlang-unicode/i18n]
github.com
i18n - icu nif: international components for unicode from Erlang (unicode, date, string, number, format, locale, localization, transliteration, icu4e)
 
icu is problematic in the fact that it works mostly with UTF-16.
 
Michał


More information about the erlang-questions mailing list