[erlang-questions] misultin on erlang R13B04?

Wilson MacGyver <>
Mon Sep 5 11:43:53 CEST 2011


No problem, as long as it's an expected behavior, I can live with that.
You may want to put in the docs that it requires R14+.

Thanks,

On Mon, Sep 5, 2011 at 3:57 AM, Roberto Ostinelli <> wrote:
> Hi Wilson,
>
> all the issues you are referring to concern type specs definitions.
>
> On R13, tid() was a built-in type, and it has been changed on R14 to be a
> remote type [which in my opinion is more correct]. Thus the error you are
> getting while compiling on R13.
>
> I did report this question here:
> http://erlang.org/pipermail/erlang-questions/2011-August/060838.html
>
> Kostis answered "But I would really recommend to the users of R13 to switch
> to R14. There are many good reasons to do that". It's not the first time I
> hear this, even the OTP team has recommended on many occasions to upgrade [I
> remember some SSL issues too].
>
> Therefore, I haven't added support to R13 on misultin 0.8. At least until
> now.
>
> r.
>
>
> On Mon, Sep 5, 2011 at 3:08 AM, Wilson MacGyver <> wrote:
>>
>> Does misultin no longer support R13 series?
>>
>> I tried to build it via make
>> and get
>>
>> make
>> erlc -W -I include -o ebin src/*.erl
>> src/misultin_acceptor.erl:85: referring to built-in type tid as a
>> remote type; please take out the module name
>> src/misultin_acceptor.erl:149: referring to built-in type tid as a
>> remote type; please take out the module name
>> src/misultin_acceptor.erl:168: referring to built-in type tid as a
>> remote type; please take out the module name
>> make: *** [all] Error 1
>>
>>
>> on R14 it builds fine.
>>
>> Thanks
>



-- 
Omnem crede diem tibi diluxisse supremum.



More information about the erlang-questions mailing list