[erlang-questions] guard expression restriction
Fri Dec 3 18:19:24 CET 2010
I think most useful guards expressions can be composed from guards.
Using macros you can bundle these and parameterize them to get
'user-defined' guards. You can then put these macros in a header and
Macros seem like a practical solution to this problem.
Am I missing something?
On Friday, December 3, 2010, James Churchman <> wrote:
> would it have to be "silently changed".. RefactorErl, Wrangler or Dialyzer could be modified to "upgrade" or at least produce warning in all* cases where flipping the functionality would effect the true functionality of it. Also i would guess much code is written with out the knowledge that some LC guards fail silently, some don't :-)
> *all in this case means "i assume all"
> On 3 Dec 2010, at 09:36, Robert Virding wrote:
>> I wonder what would happen if it was just silently changed? :-)
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:
More information about the erlang-questions