BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. Scrum
  2. Apache Maven 2
  3. Essential MySQL
  4. Node.js
  5. Groovy
  1. jQuery Selectors
  2. Ajax
  3. Java
  4. Spring Config.
  5. Java Concurrency

Link Details

Link 99892 thumbnail
User 214988 avatar

By puredanger
via weblog.hypotheticalabs.com
Published: Aug 01 2008 / 04:52

A realization hit me this morning while I was brushing my teeth. I was meditating on the relationship between classes and objects in OO languages and Erlang’s modules and processes.
  • 15
  • 0
  • 1374
  • 0

Comments

Add your comment
User 237027 avatar

AlainODea replied ago:

0 votes Vote down Vote up Reply

I think this is something Java and Erlang developers can finally agree on. OO is a good thing. I got the false impression that this approach is considered bad practice in Erlang. Upon review this OO approach to using processes is used extensively in the standard library and is the foundation of the OTP behaviours.

I think this differentiates Erlang from other functional programming languages. Erlang's processes and message-passing effectively makes OO abstractions easy that I imagine would be a hassle in pure FP languages.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.