otp.git/lib/syntax_tools, branch OTP_R15B Mirror of Erlang/OTP repository. Prepare release 2011-12-12T17:14:34+00:00 Erlang/OTP otp@erlang.org 2011-12-12T17:14:34+00:00 b92ea63417bc6933393a3c285faf393b3d287ac2 






Revert "Update version numbers for pre-release of R15"
2011-11-22T11:00:40+00:00

Björn-Egil Dahlberg
egil@erlang.org

2011-11-22T11:00:40+00:00

021472220ed3afe5a9c8e0ea854bf47f9764539c

This reverts commit e21ff9b0b69219ab3853be7e80813156113152b7.





This reverts commit e21ff9b0b69219ab3853be7e80813156113152b7.







Update version numbers for pre-release of R15
2011-11-22T10:54:29+00:00

Björn Gustavsson
bjorn@erlang.org

2011-11-21T12:59:36+00:00

e21ff9b0b69219ab3853be7e80813156113152b7












EEP-23: Allow variables in fun M:F/A
2011-11-07T12:57:03+00:00

Björn Gustavsson
bjorn@erlang.org

2010-04-09T13:50:17+00:00

ff432e262e65243cbc983fcb002527f8fae8c78b

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





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







Remove unused */doc/src/make.dep files
2011-10-27T10:52:58+00:00

Björn Gustavsson
bjorn@erlang.org

2011-10-20T12:17:52+00:00

c8053ef7b602e8c47b6fa8919b9bbff996d3a81b

These dependency files was once used when building the documentation,
but are no longer needed.





These dependency files was once used when building the documentation,
but are no longer needed.







doc Makefiles: Eliminate DOCSUPPORT ifdefs
2011-10-27T10:52:54+00:00

Björn Gustavsson
bjorn@erlang.org

2011-10-20T12:30:21+00:00

688002a16af52b2348fbc9e285ef4df32ee0e5fd

Some applications still have support for an ancient documentation
build system. Eliminate the DOCSUPPORT define in otp.mk.in and the
not taken arm of the ifdefs in the Makefiles.





Some applications still have support for an ancient documentation
build system. Eliminate the DOCSUPPORT define in otp.mk.in and the
not taken arm of the ifdefs in the Makefiles.







erl_tidy: Eliminate two references to 'regexp' in the documentation
2011-10-27T10:26:50+00:00

Björn Gustavsson
bjorn@erlang.org

2011-10-26T13:37:43+00:00

3e8720728abe875683ad54fa4d93ba83df609f57












Update copyright years
2011-09-29T16:10:19+00:00

Björn-Egil Dahlberg
egil@erlang.org

2011-09-29T16:10:19+00:00

5acac472723ef5cac6a944caf7b7ec4320c003e9












Prepare release
2011-05-24T11:16:24+00:00

Erlang/OTP
otp@erlang.org

2011-05-24T11:16:24+00:00

4a5a75811e2cd590b5c94f71864a5245fd511ccf












Fix a bug in erl_recomment
2011-04-01T06:53:48+00:00

Hans Bolinder
hasse@erlang.org

2011-04-01T06:53:48+00:00

f135c4e688dba07b42024295c1f111a106a0820c

In a file containing declarations and comments without any empty lines
between them, the recomment_forms() function would associate a
multi-line comment with the declaration above it rather than the one
following it. (Thanks to Richard Carlsson.)

This bug has been reported several times. It was corrected by Kostis
Sagonas, but the fix didn't make into the R14B02 release.





In a file containing declarations and comments without any empty lines
between them, the recomment_forms() function would associate a
multi-line comment with the declaration above it rather than the one
following it. (Thanks to Richard Carlsson.)

This bug has been reported several times. It was corrected by Kostis
Sagonas, but the fix didn't make into the R14B02 release.