Debunking The Expensive Exported-Function Call Myth
Wed Mar 16 16:02:58 CET 2005
From: "Thomas Lindgren" <>
> For Erlang, there are two extra hurdles, both due to
> code loading.
Just a thought: one could envision a code loading system that would check the
type signatures of exported functions and the types of the arguments to external
calls from that module, and only accept values that fit with the existing ones.
This would make Erlang almost statically typed, though, and also still has a
problem: several interdependent modules should be possible to be reloaded at the
same time even if type signatures are different, if those changes are only for
"intra-cluster" calls. Solvable, but not easy at all.
More information about the erlang-questions