[mercury-users] Erlang backend

[Peter Ross]

On Wed, Feb 4, 2009 at 10:25 AM, Richard O'Keefe <ok at cs.otago.ac.nz> wrote:
>
> On 3 Feb 2009, at 5:27 pm, Peter Wang wrote:
>>
>> Unfortunately it was too slow so we (Mission Critical) lost interest.  The
>> main
>> problem was, as I recall, Erlang's treatment of static data.  To implement
>> RTTI
>> and typeclasses we need some tables, which we generated as Erlang
>> functions
>> returning tuples.  With the standard Erlang compiler those tuples (which
>> can be
>> rather large) would be reconstructed each time the function was called.
>>  HiPE
>> was better, but (I think at that time) tuples containing binaries wouldn't
>> be
>> statically allocated.
>
> I am informed that
> "In R12B, constant terms (for instance, {a,b,c,[e,f,g]} or {a,<<1,2,3>>})
> are stored in a constant pool and not reconstructed every time.
> That includes binaries. (The same mechanism is used for both
> BEAM code and native code.)"
>
> The current release is R12B-5.
>
Do you know if that include constant terms which contain closures?

The RTTI includes closures which are the unification and comparison
predicates for the given type.
--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------