# compile

### MODULE

compile

### MODULE SUMMARY

Erlang Compiler

### DESCRIPTION

This module provides an interface to the standard Erlang compiler. It can generate either a new file which contains the object code, or return a binary which can be loaded directly.

### EXPORTS

`file(File)`

Is the same as `file(File, [verbose,report_errors,report_warnings])`.

`file(File, Options) -> CompRet`

Types:

`CompRet = ModRet | BinRet | ErrRet`
`ModRet = {ok,ModuleName} | {ok,ModuleName,Warnings}`
`BinRet = {ok,ModuleName,Binary} | {ok,ModuleName,Binary,Warnings}`
`ErrRet = error | {error,Errors,Warnings}`

Compiles the code in the file `File`, which is an Erlang source code file without the `.erl` extension. `Options` determine the behavior of the compiler.

Returns `{ok,ModuleName}` if successful, or `error` if there are errors. An object code file is created if the compilation succeeds with no errors.

As a step in the compilation of Erlang code, `erl_lint` is run, resulting in warning and error messages, if appropriate. The elements of `Options`, including the options relevant to the syntactic and semantic controls of `erl_lint`, can be selected as follows:

`binary`
  Causes the compiler to return the object code in a binary instead of creating an object file. If successful, the compiler returns `{ok,ModuleName,Binary}`
`debug_info`
  Include debug information in the compiled beam module. Currently, the only Erlang/OTP applications that use the debug information are Xref and Debugger.
  Warning: Note that the source code can be reconstructed from the abstract code. Therefore, never include debug information if you want to keep the source code secret.
`'P'`
  Produces a listing of the parsed code after preprocessing and parse transforms, in the file `<File>.P`. No object file is produced.
`'E'`
  Produces a listing of the code after all source code transformations have been performed, in the file `<File>.E`. No object file is produced.
`'S'`
  Produces a listing of the assembler code in the file `<File>.S`. No object file is produced.
`report_errors/report_warnings`
  Causes errors/warnings to be printed as they occur.
`report`
  This is a short form for both `report_errors` and `report_warnings`.
`return_errors`
  If this flag is set, then `{error,ErrorList,WarningList}` is returned when there are errors.
`return_warnings`
  If this flag is set, then an extra field containing `WarningList` is added to the tuples returned on success.
`return`
  This is a short form for both `return_errors` and `return_warnings`.
`verbose`
  Causes more verbose information from the compiler describing what it is doing.
`{outdir,Dir}`
  Sets a new directory for the object code. The current directory is used for output, except when a directory has been specified with this option.
`export_all`
  Causes all functions in the module to be exported.
`{i,Dir}`
  Add `Dir` to the list of directories to be searched when including a file. When encountering an `-include` or `-include_dir` directive, the compiler searches for header files in the following directories:
  1. `"."`, the current working directory of the file server;
  2. the base name of the compiled file;
  3. the directories specified using the `i` option. The directory specified last is searched first.
`{d,Macro}`
`{d,Macro,Value}`
  Defines a macro `Macro` to have the value `Value`. The default is `true`).
`{parse_transform,Module}`
  Causes the parse transformation function `Module:parse_transform/2` to be applied to the parsed code before the code is checked for errors.
`asm`
  The input file is expected to be assembler code (default file suffix ".S"). Note that the format of assembler files is not documented, and may change between releases - this option is primarily for internal debugging use.
`{warn_format, Verbosity}`
  Causes warnings to be emitted for malformed format strings as arguments to `io:format` and similar functions. `Verbosity` selects the amount of warnings: 0 = no warnings; 1 = warnings for invalid format strings and incorrect number of arguments; 2 = warnings also when the validity could not be checked (for example, when the format string argument is a variable). The default verbosity is 1. Verbosity 0 can also be selected by the option `nowarn_format`.
`warn_unused_vars`
  Causes warnings to be emitted for variables which are not used, with the exception of variables beginning with an underscore ("Prolog style warnings"). No warnings for unused variables, which is the default, can be selected by the option `nowarn_unused_vars`.
`warn_export_vars`
  Causes warnings to be emitted for all implicitly exported variables referred to after the primitives where they were first defined. No warnings for exported variables unless they are referred to in some pattern, which is the default, can be selected by the option `nowarn_export_vars`.
`warn_shadow_vars`
  Causes warnings to be emitted for "fresh" variables in functional objects or list comprehensions with the same name as some already defined variable. The default is to warn for such variables. No warnings for shadowed variables can be selected by the option `nowarn_shadow_vars`.
`warn_unused_import`
  Causes warnings to be emitted for unused imported functions. No warnings for imported functions, which is the default, can be selected by the option `nowarn_unused_import`.
`ignore_try`
  `try` is a reserved keyword from the R9 release and may not be used as atom names or field names in records (unless single-quoted). To compile old code where `try` is used, the `ignore_try` can be given.
`ignore_cond`
  `cond` is a reserved keyword starting with the R9 release and may not be used as atom names or field names in records (unless single-quoted). To compile old code where `cond` is used, the `ignore_cond` can be given.

Note that all the options except the include path ({i, Dir}) can also be given in the file with a `-compile([Option,...])`. attribute.

For debugging of the compiler, or for pure curiosity, the intermediate code generated by each compiler pass can be inspected. A complete list of the options to produce list files can be printed by typing `compile:options()` at the Erlang shell prompt. The options will be printed in order that the passes are executed. If more than one listing option is used, the one representing the earliest pass takes effect.

Unrecognized options are ignored.

Both `WarningList` and `ErrorList` have the following format:

    [{FileName,[ErrorInfo]}].

`ErrorInfo` is described below. The file name has been included here as the compiler uses the Erlang pre-processor `epp`, which allows the code to be included in other files. For this reason, it is important to know to which file an error or warning line number refers.

`forms(Forms)`

Is the same as `forms(File, [verbose,report_errors,report_warnings])`.

`forms(Forms, Options) -> CompRet`

Types:

`Forms = [Form]`
`CompRet = ModRet | BinRet | ErrRet`
`ModRet = {ok,ModuleName} | {ok,ModuleName,Warnings}`
`BinRet = {ok,ModuleName,Binary} | {ok,ModuleName,Binary,Warnings}`
`ErrRet = error | {error,Errors,Warnings}`

Analogous to `file/1`, but takes a list of forms (in the Erlang abstract format representation) as first argument. The option `binary` is implicit; i.e., no object code file is produced. If the options indicate that a listing file should be produced (e.g., 'E'), the module name is taken as the file name.

`format_error(ErrorDescriptor) -> string()`

Types:

`ErrorDescriptor = errordesc()`

Uses an `ErrorDescriptor` and returns a string which describes the error. This function is usually called implicitly when an `ErrorInfo` structure is processed. See below.

### Default compiler options

The (host operating system) environment variable `ERL_COMPILER_OPTIONS` can be used to give default compiler options. Its value must be a valid Erlang term. If the value is a list, it will be used as is. If it is not a list, it will be put into a list. The list will be appended to any options given to `file/2` or `forms/2`.

### Inlining

The compiler can now do function inlining within an Erlang module. Inlining means that a call to a function is replaced with the function body with the arguments replaced with the actual values. The semantics are preserved, except if exceptions are generated in the inlined code. Exceptions will be reported as occurring in the function the body was inlined into. Also, `function_clause` exceptions will be converted to similar `case_clause` exceptions.

When a function is inlined, the original function may be kept as a separate function as well, because there might still be calls to it. Therefore, inlining almost always increases code size.

Inlining does not necessarily improve running time. For instance, inlining may increase Beam stack usage which will probably be detrimental to performance for recursive functions.

Inlining is never default; it must be explicitly enabled with a compiler option or a '`-compile()`' attribute in the source module.

To enable inlining, use the '`inline`' option.

Example:

    -compile(inline).

The '`{inline_size,Size}`' option controls how large functions that are allowed to be inlined. Default is `24`, which will keep the size of the inlined code roughly the same as the un-inlined version (only relatively small functions will be inlined).

Example:

    %% Aggressive inlining - will increase code size.
    -compile(inline).
    -compile({inline_size,100}).

### Parse Transformations

Parse transformations are used when a programmer wants to use Erlang syntax but with different semantics. The original Erlang code is then transformed into other Erlang code.

### Error Information

The `ErrorInfo` mentioned above is the standard `ErrorInfo` structure which is returned from all IO modules. It has the following format

        {ErrorLine, Module, ErrorDescriptor}

A string describing the error is obtained with the following call:

    apply(Module, format_error, ErrorDescriptor)

### See Also

epp(3), erl_id_trans(3), erl_lint(3)

### AUTHORS

Bjorn Gustavsson - support@erlang.ericsson.se

compiler 4.1.1
Copyright © 1991-2003 Ericsson Utvecklings AB