[erlang-questions] Re: Will parameterized modules become an official part of Erlang?

[Tuncer Ayaz]

On Mon, Feb 22, 2010 at 4:43 AM, Andrew Thompson <andrew@REDACTED> wrote:
> Personally I'd list them in this order (of increasing dislike):
>
> * -extends - this one doesn't really affect you unless you're using it
>  yourself - the end user doesn't have to care (although writing a
>  behaviour is probably just as good).
> * packages - these can affect you if you're using a library that someone
>  decided to use packages in but you can probably think of them as just
>  modules with dots in the name.
> * parameterized modules - these are the ones that really screw with the
>  end user. I had a real headache when I first tried to use them in
>  mochiweb.

If you want an alternative to Mochiweb or Misultin that
doesn't use procdict, parmods and is also packaged as
an OTP app have a look at http://frihjul.net/iserve.
It is maintained by Christian Sunesson at
http://github.com/noss/iserve.

> Basicially since I wouldn't use any of them in any of my projects I
> mainly look at them from the point of view of the inconvienience when I
> try to use someone else's code that uses them.