[erlang-questions] Are packaged modules the way to go ?
Mon Dec 29 03:14:42 CET 2008
This mail is about packaged modules (module with namespace), aimed to
extend Erlang with structured module packages .
You can find a quick introduction  and the packages module
Using packaged modules or not has little impact on code but quite big
- project file structure and naming
- tools analyzing Erlang files or project file structure (such as
debugger, dialyzer, Emakefile, etc.).
- and consequently on package structure (I mean Erlang software
packaging here, such as done by CEAN ).
The support for packaged module has been introduced in Erlang/OTP before
2003 for evaluation purpose , but its adoption (or the intent of
adoption) seems still unclear today.
So my question is: for the sake of Erlang software consistency, should
Erlang developers - be it core developers or developers using Erlang -
adopt packaged modules ?
Does it need improvement before official adoption ? Should packaged
modules be ignored (or even removed from Erlang?) instead ?
 http://erlang.org/doc/man/packages.html ; For some reason exported
methods are not documented.
More information about the erlang-questions