[erlang-questions] Documentation for list_to_binary

[Juan Facorro]

Hi Paulo,

I might be doing something wrong here but the *Description* section I see 
in http://www.erlang.org/doc/man/erlang.html is the following:

DESCRIPTION

By convention, most built-in functions (BIFs) are seen as being in the 
module erlang. A number of the BIFs are viewed more or less as part of the 
Erlang programming language and are *auto-imported*. Thus, it is not 
necessary to specify the module name and both the callsatom_to_list(Erlang)
 and erlang:atom_to_list(Erlang) are identical.

In the text, auto-imported BIFs are listed without module prefix. BIFs 
listed with module prefix are not auto-imported.

BIFs may fail for a variety of reasons. All BIFs fail with reason badarg if 
they are called with arguments of an incorrect type. The other reasons that 
may make BIFs fail are described in connection with the description of each 
individual BIF.

Some BIFs may be used in guard tests, these are marked with "Allowed in 
guard tests".
I couldn't find the reference to *erlang(3)* you mention.

Cheers,

Juan

On Wednesday, June 25, 2014 11:04:39 AM UTC-3, Paulo F. Oliveira wrote:
>
> Hi. 
>
> Using Google to search for "erlang list_to_binary" the first result I 
> get is http://www.erlang.org/doc/man/erlang.html, which states, in the 
> Description "The module erlang is moved to the runtime system 
> application. Please see erlang(3) in the erts reference manual 
> instead." 
>
> The link presented by erlang(3) points to the same page. Is this normal? 
>
> Thanks. Cheers. 
>
> - Paulo F. Oliveira 
> _______________________________________________ 
> erlang-questions mailing list 
> erlang-q...@REDACTED <javascript:> 
> http://erlang.org/mailman/listinfo/erlang-questions 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140626/30f55ab9/attachment.htm>