From 334e4acd61605111712edefe874f98d030f0d25c Mon Sep 17 00:00:00 2001
From: Patrik Nyblom By default, the compiler will issue an error or warning
- when replacing an auto-imported BIF. For local functions
- having names clashing with an auto-imported BIF, the error
- or warning is issued whenever it is called without using a
- module prefix. For explicitly imported functions, the
- error or warning will be issued as soon as it's imported
- (regardless of calls). If the auto-imported BIF was present
- before OTP R14A it will be a fatal error to override it,
- otherwise only a warning will be issued. This option is removed, it will generate a fatal error if used. Beginning with R14A, the compiler no longer calls the
auto-imported BIF if the name clashes with a local or
explicitly imported function and a call without explicit
module name is issued. Instead the local or imported
- function is called. Use of
The use of this option has always been strongly discouraged. - From OTP R14A and forward it's also deprecated.
-The only module who actually could have some legitimate use for
- this option is the module
To resolve BIF clashes, use explicit module names or the
-
Turns off warnings as
This option is removed, it will generate a fatal error if used.
+The use of this option has always been strongly discouraged. - From OTP R14A and forward it's also deprecated and a warning will be issued - whenever it is used.
+ From OTP R14A and forward it's an error to use it.To resolve BIF clashes, use explicit module names or the
-