Hello!<br><br>We love patches which makes the documentation clearer for others to understand. If you have the time, please contribute to make Erlang/OTP better by submitting a patch expanding the relevant documentation. You can find the section here: <a href="https://github.com/erlang/otp/blob/master/erts/doc/src/match_spec.xml">https://github.com/erlang/otp/blob/master/erts/doc/src/match_spec.xml</a><br>
<br>Info about how to submit a patch can be found here: <a href="https://github.com/erlang/otp/wiki/Submitting-patches">https://github.com/erlang/otp/wiki/Submitting-patches</a><br><br>Lukas<br>Erlang/OTP Team<br><br><div class="gmail_quote">
On Sat, Nov 12, 2011 at 6:07 AM, wrp <span dir="ltr"><<a href="mailto:i3text@gmail.com">i3text@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
On Nov 11, 8:29 pm, Daniel Dormont <<a href="mailto:d...@greywallsoftware.com">d...@greywallsoftware.com</a>> wrote:<br>
> Erlang also has reserved words. If I were revising the manual, I would<br>
> modify section 2.3 to explicitly say "or if it is a reserved word"<br>
> with a link to the list of reserved words, which includes both 'and'<br>
> and 'andalso'.<br>
<br>
</div>AH, HA! That's it, and the list of reserved words is:<br>
after begin bsr cond if or rem<br>
and bnot bxor div let orelse try<br>
andalso bor case end not query when<br>
band bsl catch fun of receive xor<br>
<div class="HOEnZb"><div class="adm"><div id="q_133963f48091765b_2" class="ajR h4"><div class="ajT"></div></div></div><div class="h5"><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>
</div></div></blockquote></div><br>