[erlang-questions] Re: Library management in erlang.

Dale Harvey <>
Tue May 18 19:08:24 CEST 2010


On 18 May 2010 18:01, Bob Ippolito <> wrote:

> On Tue, May 18, 2010 at 8:36 AM, Nicholas Frechette <>
> wrote:
> > IMO, it is premature to talk about an erlang library management system
> when
> > the risk of module name collision is so high. We'd have to
> require/enforce a
> > package prefix in the form of 'packagename_' to all modules of a package.
>
> Many (most?) packages already do this, so it's not really a problem.
>
> > That is until erlang has an approved package/namespace system (the one
> > currently implemented is experimental and discussed in another thread
> atm).
>
> There's plenty other global resources you can run into that aren't
> just module names, e.g. processes or applications. Picking a namespace
> syntax doesn't fix that.
>
>
and the erlang "application" infrastructure already warns(errors?) against
conflicts in module names / global processes etc.

As long as the library management system was based around .app files, doesnt
seem like there would be a problem


> Also if you don't install packages system-wide, you're even less
> likely to have a problem. You could use something like Basho's rebar
> to manage application installs with dependencies.
>
> -bob
>
> ________________________________________________________________
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:
>
>


More information about the erlang-questions mailing list