[erlang-questions] (Non)Parametrized modules, inheritance, and R15B02 issues?

Gordon Guthrie gordon@REDACTED
Mon Oct 8 15:00:34 CEST 2012


> Are you sure?

Uh, no, I am not sure - I thought I was :(

I had better find out.

>> So is the general advice that everybody should migrate away from Mochiweb?
>
> No, it is not. It is a recommendation to think twice about using
> experimental fetures when writing new code or fixing old code.

Yeah, but the point of building on libraries is so as not to write code at all..

G


On 8 October 2012 13:56, Björn Gustavsson <bgustavsson@REDACTED> wrote:
> On Mon, Oct 8, 2012 at 2:24 PM, Gordon Guthrie <gordon@REDACTED> wrote:
>> We use Mochiweb which makes extensive use of them.
>
> Are you sure? What I have understood from previous email
> messages on this list is that many projects use "tuple modules"
> (which is an implementation detail in parameterized modules)
> and not parameterized modules directly. See for instance:
>
> http://erlang.org/pipermail/erlang-questions/2012-January/063915.html
>
> We are thinking about removing the compiler support for parameterized
> modules, but keeping the low-level mechanism in erlang:apply/3 and
> the inheritance hack in the error_handler module.
>
>> So is the general advice that everybody should migrate away from Mochiweb?
>
> No, it is not. It is a recommendation to think twice about using
> experimental fetures when writing new code or fixing old code.
>
>
> --
> Björn Gustavsson, Erlang/OTP, Ericsson AB



More information about the erlang-questions mailing list