diff options
author | Björn Gustavsson <[email protected]> | 2010-04-09 15:50:17 +0200 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2011-11-07 13:57:03 +0100 |
commit | ff432e262e65243cbc983fcb002527f8fae8c78b (patch) | |
tree | 1966b14f94663375eb0333c3e2d707aab501a960 /EPLICENCE | |
parent | 33c08d87a9395ae088eebcad9fb62193d26b6846 (diff) | |
download | otp-ff432e262e65243cbc983fcb002527f8fae8c78b.tar.gz otp-ff432e262e65243cbc983fcb002527f8fae8c78b.tar.bz2 otp-ff432e262e65243cbc983fcb002527f8fae8c78b.zip |
EEP-23: Allow variables in fun M:F/A
Currently, the external fun syntax "fun M:F/A" only supports
literals. That is, "fun lists:reverse/1" is allowed but not
"fun M:F/A".
In many real-life situations, some or all of M, F, A are
not known until run-time, and one is forced to either use
the undocumented erlang:make_fun/3 BIF or to use a
"tuple fun" (which is deprecated).
EEP-23 suggests that the parser (erl_parse) should immediately
transform "fun M:F/A" to "erlang:make_fun(M, F, A)". We have
not followed that approach in this implementation, because we
want the abstract code to mirror the source code as closely
as possible, and we also consider erlang:make_fun/3 to
be an implementation detail that we might want to remove in
the future.
Instead, we will change the abstract format for "fun M:F/A" (in a way
that is not backwards compatible), and while we are at it, we will
move the translation from "fun M:F/A" to "erlang:make_fun(M, F, A)"
from sys_pre_expand down to the v3_core pass. We will also update
the debugger and xref to use the new format.
We did consider making the abstract format backward compatible if
no variables were used in the fun, but decided against it. Keeping
it backward compatible would mean that there would be different
abstract formats for the no-variable and variable case, and tools
would have to handle both formats, probably forever.
Reference: http://www.erlang.org/eeps/eep-0023.html
Diffstat (limited to 'EPLICENCE')
0 files changed, 0 insertions, 0 deletions