Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

erl_internal(3erl) [linux man page]

erl_internal(3erl)					     Erlang Module Definition						erl_internal(3erl)

NAME
erl_internal - Internal Erlang Definitions DESCRIPTION
This module defines Erlang BIFs, guard tests and operators. This module is only of interest to programmers who manipulate Erlang code. EXPORTS
bif(Name, Arity) -> bool() Types Name = atom() Arity = integer() Returns true if Name/Arity is an Erlang BIF which is automatically recognized by the compiler, otherwise false . guard_bif(Name, Arity) -> bool() Types Name = atom() Arity = integer() Returns true if Name/Arity is an Erlang BIF which is allowed in guards, otherwise false . type_test(Name, Arity) -> bool() Types Name = atom() Arity = integer() Returns true if Name/Arity is a valid Erlang type test, otherwise false . arith_op(OpName, Arity) -> bool() Types OpName = atom() Arity = integer() Returns true if OpName/Arity is an arithmetic operator, otherwise false . bool_op(OpName, Arity) -> bool() Types OpName = atom() Arity = integer() Returns true if OpName/Arity is a Boolean operator, otherwise false . comp_op(OpName, Arity) -> bool() Types OpName = atom() Arity = integer() Returns true if OpName/Arity is a comparison operator, otherwise false . list_op(OpName, Arity) -> bool() Types OpName = atom() Arity = integer() Returns true if OpName/Arity is a list operator, otherwise false . send_op(OpName, Arity) -> bool() Types OpName = atom() Arity = integer() Returns true if OpName/Arity is a send operator, otherwise false . op_type(OpName, Arity) -> Type Types OpName = atom() Arity = integer() Type = arith | bool | comp | list | send Returns the Type of operator that OpName/Arity belongs to, or generates a function_clause error if it is not an operator at all. Ericsson AB stdlib 1.17.3 erl_internal(3erl)

Check Out this Related Man Page

eprof(3erl)						     Erlang Module Definition						       eprof(3erl)

NAME
eprof - A Time Profiling Tool for Erlang DESCRIPTION
The module eprof provides a set of functions for time profiling of Erlang programs to find out how the execution time is used. The profil- ing is done using the Erlang trace BIFs. Tracing of local function calls for a specified set of processes is enabled when profiling is begun, and disabled when profiling is stopped. When using Eprof expect a slowdown in program execution. EXPORTS
start() -> {ok,Pid} | {error,Reason} Types Pid = pid() Reason = {already_started,Pid} Starts the Eprof server which holds the internal state of the collected data. start_profiling(Rootset) -> profiling | {error, Reason} start_profiling(Rootset,Pattern) -> profiling | {error, Reason} Types Rootset = [atom() | pid()] Pattern = {Module, Function, Arity} Module = Function = atom() Arity = integer() Reason = term() Starts profiling for the processes in Rootset (and any new processes spawned from them). Information about activity in any profiled process is stored in the Eprof database. Rootset is a list of pids and registered names. The function returns profiling if tracing could be enabled for all processes in Rootset , or error otherwise. A pattern can be selected to narrow the profiling. For instance ca a specific module be selected and only the code processes exe- cutes in that module will be profiled. stop_profiling() -> profiling_stopped | profiling_already_stopped Stops profiling started with start_profiling/1 or profile/1 . profile(Fun) -> profiling | {error, Reason} profile(Rootset) -> profiling | {error, Reason} profile(Rootset,Fun) -> {ok, Value} | {error,Reason} profile(Rootset,Fun,Pattern) -> {ok, Value} | {error, Reason} profile(Rootset,Module,Function,Args) -> {ok, Value} | {error, Reason} profile(Rootset,Module,Function,Args,Pattern) -> {ok, Value} | {error, Reason} Types Rootset = [atom() | pid()] Fun = fun() -> term() Pattern = {Module, Function, Arity} Module = Function = atom() Args = [term()] Arity = integer() Value = Reason = term() This function first spawns a process P which evaluates Fun() or apply(Module,Function,Args) . Then, it starts profiling for P and the processes in Rootset (and any new processes spawned from them). Information about activity in any profiled process is stored in the Eprof database. Rootset is a list of pids and registered names. If tracing could be enabled for P and all processes in Rootset , the function returns {ok,Value} when Fun() / apply returns with the value Value , or {error,Reason} if Fun() / apply fails with exit reason Reason . Otherwise it returns {error, Reason} immediately. The programmer must ensure that the function given as argument is truly synchronous and that no work continues after the function has returned a value. analyze() -> ok analyze(Type) -> ok analyze(Type,Options) -> ok Types Type = procs | total Options = [{filter, Filter} | {sort, Sort} Filter = [{calls, integer()} | {time, float()}] Sort = time | calls | mfa Call this function when profiling has been stopped to display the results per process, that is: * how much time has been used by each process, and * in which function calls this time has been spent. Call analyze with total option when profiling has been stopped to display the results per function call, that is in which function calls the time has been spent. Time is shown as percentage of total time and as absolute time. log(File) -> ok Types File = atom() | string() This function ensures that the results displayed by analyse/0 and total_analyse/0 are printed both to the file File and the screen. stop() -> stopped Stops the Eprof server. Ericsson AB tools 2.6.6.3 eprof(3erl)
Man Page