[erlang-bugs] module name with .
Mon Mar 1 04:19:46 CET 2010
Ah, so there is documentation. But I must say it has been put in a
place where I would definitely not look for it, among the kernel
documentation, as it is not something you call.
And I think that as it is something experimental you should have to
turn it on to use it, it should not *always* be there. The two other
experimental features, parametrised modules and extends, are better in
this respect in that you actually have to explicitly do something to
There was another thread which discussed the existence of parametrised
modules and packages briefly appeared there as well (introduced by
me). And, as I stated there, I don't see the need for either of them.
On 28 February 2010 18:29, Richard Carlsson <> wrote:
> Not that poorly documented (under kernel):
> And no, you can't have a source file named "fm2.2.erl".
> Robert Virding wrote:
>> My guess is that you are interacting with the experimental, and poorly
>> documented, package system which assumes things when it sees module
>> names with '.'. As far as I know there is no way to turn this off.
>> Someone else may know more about this. My only suggestion is to avoid
>> module names with a '.'.
>> On 28 February 2010 10:09, J K <> wrote:
>>> is this a bug?
>>> Erlang R13B01 (erts-5.7.2) [smp:2:2] [rq:2] [async-threads:0]
>>> Eshell V5.7.2 (abort with ^G)
>>> 4> c('fm2.2').
>>> fm2.2.beam: Module name 'fm2.2' does not match file name 'fm2.2'
>>> i have:
More information about the erlang-bugs