From 31f85c90ac02cfa8bd6c60fb8d940acbeeeea904 Mon Sep 17 00:00:00 2001
From: Patrik Nyblom
Date: Mon, 20 Sep 2010 16:28:48 +0200
Subject: Correct description of no_auto_import compiler directive
---
lib/compiler/doc/src/compile.xml | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
(limited to 'lib/compiler')
diff --git a/lib/compiler/doc/src/compile.xml b/lib/compiler/doc/src/compile.xml
index e1f24b602d..c3d65b4cb5 100644
--- a/lib/compiler/doc/src/compile.xml
+++ b/lib/compiler/doc/src/compile.xml
@@ -310,9 +310,9 @@
(there will not even be a warning if there is a mismatch).
- {no_auto_import,[F/A, ...]}
+ {no_auto_import,[{F,A}, ...]}
-
-
Makes the function F/A no longer beeing
+
Makes the function F/A no longer being
auto-imported from the module erlang, which resolves
BIF name clashes. This option has to be used to resolve name
clashes with BIFs auto-imported before R14A, if one wants to
@@ -323,8 +323,12 @@
without module prefix to local or imported functions before
trying auto-imported BIFs. If the BIF is to be
called, use the erlang module prefix in the call, not
- { no_auto_import,[F/A, ...]}
+ { no_auto_import,[{F,A}, ...]}
+ If this option is written in the source code, as a
+ -compile directive, the syntax F/A can be used instead
+ of {F,A}. Example:
+ -compile({no_auto_import,[error/1]}).
--
cgit v1.2.3