aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTuncer Ayaz <[email protected]>2013-12-03 19:16:16 +0100
committerBjörn Gustavsson <[email protected]>2013-12-18 10:26:55 +0100
commit455c8238535d2754234cd68bbf7caba9960607d6 (patch)
tree353cf81814416569c645236a20fa2f8daff6d94f
parent18315c1675d965e5d0210a560e4742c483fcfd7f (diff)
downloadotp-455c8238535d2754234cd68bbf7caba9960607d6.tar.gz
otp-455c8238535d2754234cd68bbf7caba9960607d6.tar.bz2
otp-455c8238535d2754234cd68bbf7caba9960607d6.zip
Officially support building core files
erlc is wired to treat *.core files as core and build them as compile:file(File, [from_core]), but this is not documented. There's also an udocumented compile:file/2 option called 'from_core'. This has been in place and in use for a long time. Therefore, it should be supported officially. To fix that, make the following changes: * document erlc handling of *.core files * document 'from_core'
-rw-r--r--erts/doc/src/erlc.xml5
-rw-r--r--lib/compiler/doc/src/compile.xml7
2 files changed, 12 insertions, 0 deletions
diff --git a/erts/doc/src/erlc.xml b/erts/doc/src/erlc.xml
index 2df026aef5..c3fc3b1686 100644
--- a/erts/doc/src/erlc.xml
+++ b/erts/doc/src/erlc.xml
@@ -239,6 +239,11 @@ erlc +export_all file.erl</pre>
<p>Erlang assembler source code. It generates a <c><![CDATA[.beam]]></c> file.</p>
<p>Supported options: same as for .erl.</p>
</item>
+ <tag>.core</tag>
+ <item>
+ <p>Erlang core source code. It generates a <c><![CDATA[.beam]]></c> file.</p>
+ <p>Supported options: same as for .erl.</p>
+ </item>
<tag>.yrl</tag>
<item>
<p>Yecc source code. It generates an <c><![CDATA[.erl]]></c> file.</p>
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index eb7745890e..1459f696a0 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -357,6 +357,13 @@ module.beam: module.erl \
is not documented, and may change between releases.</p>
</item>
+ <tag><c>from_core</c></tag>
+ <item>
+ <p>The input file is expected to be core code (default
+ file suffix ".core"). Note that the format of core files
+ is not documented, and may change between releases.</p>
+ </item>
+
<tag><c>no_strict_record_tests</c></tag>
<item>
<p>This option is not recommended.</p>