[erlang-bugs] Local function names in Core Erlang guards
Mon Nov 19 12:24:45 CET 2012
It's a core_lint bug! Erlang (and core and the BEAM) does not permit calling user defined functions in a guard.
The core scanning/parsing/linting was added to allow people to write code directly in Core erlang. As far as I know no one does.
----- Original Message -----
> From: "Anthony Ramine" <>
> Cc: "Bjorn Gustavsson" <>
> Sent: Monday, 19 November, 2012 11:02:42 AM
> Subject: [erlang-bugs] Local function names in Core Erlang guards
> While patching the compiler to allow substitutions of variables which
> values are
> local function names , I discovered that core_lint doesn't forbid
> them in guards,
> even though that makes the compiler passes further down the road
> generate badly-formed
> BEAM code.
> Is that a bug in core_lint or a bug in the BEAM code generation?
> Should local function
> names be allowed in guards?
> If it is a bug in core_lint, I can make a patch for that; if it is a
> bug in the BEAM
> code generation I would love to fix it and remove the code I wrote to
> avoid the
> substitution in guards... but I lack knowledge about the BEAM
> Anthony Ramine
> erlang-bugs mailing list
More information about the erlang-bugs