From e4e6be433e024a54d7b1e465d90f95769a5f910c Mon Sep 17 00:00:00 2001 From: Patrik Nyblom Date: Tue, 31 Aug 2010 10:33:07 +0200 Subject: Correct erlang.xml regarding autoimports --- erts/doc/src/erlang.xml | 102 ++++++++++++++++++++++++------------------------ 1 file changed, 51 insertions(+), 51 deletions(-) (limited to 'erts/doc/src') diff --git a/erts/doc/src/erlang.xml b/erts/doc/src/erlang.xml index ba93fe34d3..59ac3dc66c 100644 --- a/erts/doc/src/erlang.xml +++ b/erts/doc/src/erlang.xml @@ -80,7 +80,7 @@ iolist() = [char() | binary() | iolist()] - adler32(Data) -> int() + erlang:adler32(Data) -> int() Compute adler32 checksum Data = iodata() @@ -90,7 +90,7 @@ iolist() = [char() | binary() | iolist()] - adler32(OldAdler, Data) -> int() + erlang:adler32(OldAdler, Data) -> int() Compute adler32 checksum OldAdler = int() @@ -102,17 +102,17 @@ iolist() = [char() | binary() | iolist()] Data.

The following code:

- X = adler32(Data1), - Y = adler32(X,Data2). + X = erlang:adler32(Data1), + Y = erlang:adler32(X,Data2).

- would assign the same value to Y as this would:

- Y = adler32([Data1,Data2]). + Y = erlang:adler32([Data1,Data2]). - adler32_combine(FirstAdler, SecondAdler, SecondSize) -> int() + erlang:adler32_combine(FirstAdler, SecondAdler, SecondSize) -> int() Combine two adler32 checksums FirstAdler = SecondAdler = int() @@ -124,14 +124,14 @@ iolist() = [char() | binary() | iolist()] the second checksum to be known.

The following code:

- Y = adler32(Data1), - Z = adler32(Y,Data2). + Y = erlang:adler32(Data1), + Z = erlang:adler32(Y,Data2).

- would assign the same value to Z as this would:

- X = adler32(Data1), - Y = adler32(Data2), - Z = adler32_combine(X,Y,iolist_size(Data2)). + X = erlang:adler32(Data1), + Y = erlang:adler32(Data2), + Z = erlang:adler32_combine(X,Y,iolist_size(Data2)). @@ -553,7 +553,7 @@ false - crc32(Data) -> int() + erlang:crc32(Data) -> int() Compute crc32 (IEEE 802.3) checksum Data = iodata() @@ -563,7 +563,7 @@ false - crc32(OldCrc, Data) -> int() + erlang:crc32(OldCrc, Data) -> int() Compute crc32 (IEEE 802.3) checksum OldCrc = int() @@ -575,17 +575,17 @@ false Data.

The following code:

- X = crc32(Data1), - Y = crc32(X,Data2). + X = erlang:crc32(Data1), + Y = erlang:crc32(X,Data2).

- would assign the same value to Y as this would:

- Y = crc32([Data1,Data2]). + Y = erlang:crc32([Data1,Data2]). - crc32_combine(FirstCrc, SecondCrc, SecondSize) -> int() + erlang:crc32_combine(FirstCrc, SecondCrc, SecondSize) -> int() Combine two crc32 (IEEE 802.3) checksums FirstCrc = SecondCrc = int() @@ -597,14 +597,14 @@ false the second checksum to be known.

The following code:

- Y = crc32(Data1), - Z = crc32(Y,Data2). + Y = erlang:crc32(Data1), + Z = erlang:crc32(Y,Data2).

- would assign the same value to Z as this would:

- X = crc32(Data1), - Y = crc32(Data2), - Z = crc32_combine(X,Y,iolist_size(Data2)). + X = erlang:crc32(Data1), + Y = erlang:crc32(Data2), + Z = erlang:crc32_combine(X,Y,iolist_size(Data2)). @@ -624,7 +624,7 @@ false - decode_packet(Type,Bin,Options) -> {ok,Packet,Rest} | {more,Length} | {error,Reason} + erlang:decode_packet(Type,Bin,Options) -> {ok,Packet,Rest} | {more,Length} | {error,Reason} Extracts a protocol packet from a binary Bin = binary() @@ -760,7 +760,7 @@ false - erlang:demonitor(MonitorRef) -> true + demonitor(MonitorRef) -> true Stop monitoring MonitorRef = reference() @@ -768,10 +768,10 @@ false

If MonitorRef is a reference which the calling process obtained by calling - erlang:monitor/2, + monitor/2, this monitoring is turned off. If the monitoring is already turned off, nothing happens.

-

Once erlang:demonitor(MonitorRef) has returned it is +

Once demonitor(MonitorRef) has returned it is guaranteed that no {'DOWN', MonitorRef, _, _, _} message due to the monitor will be placed in the callers message queue in the future. A {'DOWN', MonitorRef, _, _, _} message @@ -779,10 +779,10 @@ false the call, though. Therefore, in most cases, it is advisable to remove such a 'DOWN' message from the message queue after monitoring has been stopped. - erlang:demonitor(MonitorRef, [flush]) can be used instead of - erlang:demonitor(MonitorRef) if this cleanup is wanted.

+ demonitor(MonitorRef, [flush]) can be used instead of + demonitor(MonitorRef) if this cleanup is wanted.

-

Prior to OTP release R11B (erts version 5.5) erlang:demonitor/1 +

Prior to OTP release R11B (erts version 5.5) demonitor/1 behaved completely asynchronous, i.e., the monitor was active until the "demonitor signal" reached the monitored entity. This had one undesirable effect, though. You could never know when @@ -800,7 +800,7 @@ false - erlang:demonitor(MonitorRef, OptionList) -> true|false + demonitor(MonitorRef, OptionList) -> true|false Stop monitoring MonitorRef = reference() @@ -812,8 +812,8 @@ false

The returned value is true unless info is part of OptionList.

-

erlang:demonitor(MonitorRef, []) is equivalent to - erlang:demonitor(MonitorRef).

+

demonitor(MonitorRef, []) is equivalent to + demonitor(MonitorRef).

Currently the following Options are valid:

flush @@ -821,11 +821,11 @@ false

Remove (one) {_, MonitorRef, _, _, _} message, if there is one, from the callers message queue after monitoring has been stopped.

-

Calling erlang:demonitor(MonitorRef, [flush]) +

Calling demonitor(MonitorRef, [flush]) is equivalent to the following, but more efficient:

- erlang:demonitor(MonitorRef), + demonitor(MonitorRef), receive {_, MonitorRef, _, _, _} -> true @@ -863,7 +863,7 @@ false

Failure: badarg if OptionList is not a list, or if Option is not a valid option, or the same failure as for - erlang:demonitor/1

+ demonitor/1

 @@ -944,7 +944,7 @@ b - erlang:error(Reason) + error(Reason) Stop execution with a given reason Reason = term() @@ -957,7 +957,7 @@ b function first). Since evaluating this function causes the process to terminate, it has no return value.

-> catch erlang:error(foobar).
+> catch error(foobar).
 {'EXIT',{foobar,[{erl_eval,do_apply,5},
                  {erl_eval,expr,5},
                  {shell,exprs,6},
@@ -966,7 +966,7 @@ b
 - erlang:error(Reason, Args) + error(Reason, Args) Stop execution with a given reason Reason = term() @@ -1483,7 +1483,7 @@ os_prompt% - erlang:integer_to_list(Integer, Base) -> string() + integer_to_list(Integer, Base) -> string() Text representation of an integer Integer = int() @@ -1493,7 +1493,7 @@ os_prompt%

Returns a string which corresponds to the text representation of Integer in base Base.

-> erlang:integer_to_list(1023, 16).
+> integer_to_list(1023, 16).
 "3FF"
 @@ -1932,7 +1932,7 @@ os_prompt% - erlang:list_to_integer(String, Base) -> int() + list_to_integer(String, Base) -> int() Convert from text representation to an integer String = string() @@ -1942,7 +1942,7 @@ os_prompt%

Returns an integer whose text representation in base Base is String.

-> erlang:list_to_integer("3FF", 16).
+> list_to_integer("3FF", 16).
 1023

Failure: badarg if String contains a bad representation of an integer.

@@ -2488,7 +2488,7 @@ os_prompt% - erlang:monitor(Type, Item) -> MonitorRef + monitor(Type, Item) -> MonitorRef Start monitoring Type = process @@ -2524,7 +2524,7 @@ os_prompt%

When a process is monitored by registered name, the process that has the registered name at the time when - erlang:monitor/2 is called will be monitored. + monitor/2 is called will be monitored. The monitor will not be effected, if the registered name is unregistered.

 @@ -2558,20 +2558,20 @@ os_prompt% -

If/when erlang:monitor/2 is extended (e.g. to +

If/when monitor/2 is extended (e.g. to handle other item types than process), other possible values for Object, and Info in the 'DOWN' message will be introduced.

The monitoring is turned off either when the 'DOWN' message is sent, or when - erlang:demonitor/1 + demonitor/1 is called.

If an attempt is made to monitor a process on an older node (where remote process monitoring is not implemented or one where remote process monitoring by registered name is not implemented), the call fails with badarg.

-

Making several calls to erlang:monitor/2 for the same +

Making several calls to monitor/2 for the same Item is not an error; it results in as many, completely independent, monitorings.

@@ -3899,11 +3899,11 @@ os_prompt% {monitored_by, Pids}

A list of pids that are monitoring the process (with - erlang:monitor/2).

+ monitor/2).

 {monitors, Monitors} -

A list of monitors (started by erlang:monitor/2) +

A list of monitors (started by monitor/2) that are active for the process. For a local process monitor or a remote process monitor by pid, the list item is {process, Pid}, and for a remote process @@ -4092,7 +4092,7 @@ os_prompt% terminate, it has no return value - unless the arguments are invalid, in which case the function returns the error reason, that is badarg. If you want to be really sure not to return you can call - erlang:error(erlang:raise(Class, Reason, Stacktrace)) + error(erlang:raise(Class, Reason, Stacktrace)) and hope to distinguish exceptions later.

 @@ -4693,7 +4693,7 @@ true monitor

Monitor the new process (just like - erlang:monitor/2 does).

+ monitor/2 does).

 {priority, Level} -- cgit v1.2.3