[erlang-questions] Process scope variable

Thu Feb 19 23:21:35 CET 2015

On 02/19/2015 10:13 PM, Robert Virding wrote:
> An historical perspective: over the years there have been a number of
> attempts to add more traditional OO and classes to Erlang, and while many
> have worked they were never very long-lived. I think that that style of
> programming just doesn't fit well together with Erlang. There are a number
> of languages which mix functional and OO, for example scala, but personally
> I am sceptical to that. To really reap the benefits of functional
> programming you have to know, I mean really KNOW, that it won't be
> compromised somewhere else so that you can trust. If you can't trust it
> then what's the point, I might as while write C in a functional style.
> The bigger and more complex and more long-lived your application becomes
> the more important this is. It mightn't always feel the best but in the
> long-run and when things scale the better it becomes. And, yes of course,
> you can have programming rules but I also know that breaking a rule this
> little one time isn't going hurt anyone. Etc.

all in all you can think of an Erlang module as an object.
and it gives you much better "OOP" than traditional OOP.

More information about the erlang-questions mailing list