Re: Call with a tuple as a module succeeds in Erlang 18 RC2

Thanks Anthony & Fred!

As far as I can understand from http://www.erlang.org/news/35:

* The compiler warnings are wrong. The calls will succeed, and are expected
to do so, since tuples are supported.
* There should be 'proper documentation' about this feature somewhere, but
I have failed to find it.
* HiPE is wrong in compiling this into something that returns a 'badarg'
error.

It seems, therefore, that this is still a bug report, right?

Stavros

On Wed, May 27, 2015 at 3:07 PM, Fred Hebert <[email protected]> wrote:

> On 05/27, Anthony Ramine wrote:
>
>> From what I know, the module-as-tuple feature is here to stay and HiPE is
>> wrong to refuse to compile such code.
>>
>>
> That is correct. See http://www.erlang.org/news/35, issue 4:
>
>  Issue 4 - What to do with unsupported feature 'parameterized modules'.
>>
>> [...]
>>
>> To allow for source code compatibility, the board decides to only remove
>> the syntactic support for parameterized modules. This means:
>>
>> * Apply with tuple modules will be retained, supported and properly
>> documented.
>>
>> [...]
>>
>> * The parser will accept the syntax for implementation of parameterized
>> modules, but if the parameterized modules are not handled by a
>> parse_transform, an error message will be generated at a later stage (this
>> concerns the implementation of the modules themselves only).
>>
>>
> I kept the relevant sections of the announcement.
>

_______________________________________________
erlang-bugs mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-bugs