[erlang-questions] concurrency developments

Dmitri Girenko <>
Thu Jan 17 08:09:24 CET 2008


> What is "core Erlang"?

 

It's the Hardcore Erlang without the Hard part :-)

Just kidding.

 

 

________________________________

From: 
[mailto:] On Behalf Of David Mercer
Sent: 17. tammikuuta 2008 1:29
To: 'Robert Virding'
Cc: 
Subject: Re: [erlang-questions] concurrency developments

 

If you are going to compile down to something other than straight Erlang
then the best target is Core erlang.

 

What is "core Erlang"?

 

DBM

 

________________________________

From: 
[mailto:] On Behalf Of Robert Virding
Sent: Wednesday, January 16, 2008 16:17
To: 
Cc: 
Subject: Re: [erlang-questions] concurrency developments

 

On 16/01/2008, Bob Calco <> wrote:

	I have recently decided to experiment writing a Ruby-like front
end to Erlang, code named Emerld, which would generate Erlang code that
would then be compiled (at least until I can learn the BEAM file format
well enough to generate it directly). It could theoretically be
retargeted to .NET or Java when either of the two got their act together
for concurrency. That seems to me more a matter of when than if. Until
then though I have committed myself to mastering Erlang, because I think
it will give me a huge competitive edge in the new multi-core world we
live in as a software designer and architect.


If you are going to compile down to something other than straight Erlang
then the best target is Core erlang. It a pure relatively simple and
standard functional language which is used inside the compiler. The AST
is defined by a set of records and there are tools to read/check/print
it. As far as I know there is nothing *legal* you can do in the BEAM
code which you can't do in Core. Also you have the benefit of not being
forced to modify your compiler as the BEAM engine is improved. If I
remember correctly HIPA also uses Core for one pass in its compiler.
Someone who knows can comment. 

This is what I am doing for my LISP front-end to Erlang. Soon to be
ready.

Robert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080117/108d47f4/attachment.html>


More information about the erlang-questions mailing list