[erlang-questions] Why is Erlang what it is?
Wed Dec 13 16:55:31 CET 2006
I have thought about release handling and so on but then I saw this project.
So it was just an academic research without much results and almost no
influence on Erlang/OTP?
>From the paper:
The production version of our type checker is currently
under construction, and will be distributed along with a
future version of the Erlang system. We expect the final
version to improve on the prototype in areas of performance,
robustness and the quality of diagnostics.
But now I see no signs of something like:
-type and(bool(),bool()) -> bool().
Quite strange to me :(
On 12/13/06, Christian S <> wrote:
> On 12/13/06, Kirill Zaborski <> wrote:
> > Yeah, I know about the dialyzer. But are there any reasons why static
> > is dead?
> > Are there any papers why it was declined? Or maybe should I send an
> email to
> > Philip Wadler?
> In systems where you load code into running systems it might be overly
> to perform a complete static type check for the system with the new
> code inserted. Not that it is impossible though.
> It would motivate me to pick dynamic typing. :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions