<p>End of speculation, we have made a number of decisions for the upcoming R16B ( end of February). We will describe this in more detail on this list and on <a href="http://erlang.org">erlang.org</a><br>
next week. Parameterized modules is part of this decision, and there is no need to worry. The code using them today will continue to work.</p>
<p>But as said more details will come soon.</p>
<p>/Kenneth, Erlang/OTP Ericsson</p>
<div class="gmail_quote">---------- Vidarebefordrat meddelande ----------<br>Från: "Ulf Wiger" <<a href="mailto:ulf@feuerlabs.com">ulf@feuerlabs.com</a>><br>Datum: 12 okt 2012 19:46<br>Ämne: Re: [erlang-questions] (Non)Parametrized modules, inheritance, and R15B02 issues?<br>
Till: "Yurii Rashkovskii" <<a href="mailto:yrashk@gmail.com">yrashk@gmail.com</a>><br>Kopia: "Tomas Morstein" <<a href="mailto:tmr@idea.cz">tmr@idea.cz</a>>, <<a href="mailto:erlang-programming@googlegroups.com">erlang-programming@googlegroups.com</a>>, "<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>" <<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>><br>
<br type="attribution"><div style="word-wrap:break-word"><div><br></div><div>Oh, well… :)</div><div><br></div><div>OTOH, Björn Gustavsson himself said earlier (8 Oct):</div><div class="quoted-text"><div><br></div><div><blockquote type="cite">
Are you sure? What I have understood from previous email<br>messages on this list is that many projects use "tuple modules"<br>(which is an implementation detail in parameterized modules)<br>and not parameterized modules directly. See for instance:<br>
<br><a href="http://erlang.org/pipermail/erlang-questions/2012-January/063915.html" target="_blank">http://erlang.org/pipermail/erlang-questions/2012-January/063915.html</a><br><br>We are thinking about removing the compiler support for parameterized<br>
modules, but keeping the low-level mechanism in erlang:apply/3 and<br>the inheritance hack in the error_handler module.</blockquote><br></div></div><div>Just for fun, FWIW, I wrote a little parse transform that gives</div>
<div>roughly the same functionality as parameterized modules,</div><div>but without relying on the special syntax.</div><div><br></div><div><a href="https://github.com/uwiger/parse_trans/commit/ae7163f3dbc2d3cbf23fb9a796b7f2e576dab09a" target="_blank">https://github.com/uwiger/parse_trans/commit/ae7163f3dbc2d3cbf23fb9a796b7f2e576dab09a</a></div>
<div><br></div><div>Note how it's in parse_trans/examples/, so it's mainly for fun.</div><div>It does seem to work, though.</div><div><br></div><div>BR,</div><div>Ulf W</div><br><div><div class="quoted-text"><div>
On 12 Oct 2012, at 19:35, Yurii Rashkovskii wrote:</div><br></div><blockquote type="cite"><div class="quoted-text">From what I learned earlier this year, tuple modules have a bleak future as well:</div><div><div class="quoted-text">
<br>===<br><br>[1] > But I was wondering if there's any word out about the fate of tuple<br>> modules? The ones like {erlang}:element(1). Are they expected to be<br>> kept around? (I certainly hope they are :)<br>
><br><br>No, we don't expect to keep them.<br><br></div>[…]<br><br>/Björn</div></blockquote></div><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><div>
<div>Ulf Wiger, Co-founder & Developer Advocate, Feuerlabs Inc.</div><div><a href="http://feuerlabs.com" target="_blank">http://feuerlabs.com</a></div></div><div><br></div></span><br>
</div>
<br></div><br>_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></div>