Frama-C API - Acsl_extension
ACSL extensions registration module
type extension_preprocessor = Logic_ptree.lexpr list -> Logic_ptree.lexpr list
Untyped ACSL extensions transformers
type extension_typer = Logic_typing.typing_context -> Logic_ptree.location -> Logic_ptree.lexpr list -> Cil_types.acsl_extension_kind
Transformers from untyped to typed ACSL extension
type extension_visitor = Cil.cilVisitor -> Cil_types.acsl_extension_kind -> Cil_types.acsl_extension_kind Cil.visitAction
Visitor functions for ACSL extensions
type extension_preprocessor_block = (string * Logic_ptree.extended_decl list) -> string * Logic_ptree.extended_decl list
type extension_typer_block = Logic_typing.typing_context -> Logic_ptree.location -> (string * Logic_ptree.extended_decl list) -> Cil_types.acsl_extension_kind
type extension_module_importer = Logic_typing.module_builder -> Logic_ptree.location -> string list -> unit
type extension_printer = Printer_api.extensible_printer_type -> Stdlib.Format.formatter -> Cil_types.acsl_extension_kind -> unit
Pretty printers for ACSL extensions
type extension_same = Cil_types.acsl_extension_kind -> Cil_types.acsl_extension_kind -> Ast_diff.is_same_env -> bool
type of functions that compare two extensions (with the same keyword) to decide if they're identical or not. See Ast_diff
for more information.
type register_extension = plugin:string -> string -> ?preprocessor:extension_preprocessor -> extension_typer -> ?visitor:extension_visitor -> ?printer:extension_printer -> ?short_printer:extension_printer -> ?is_same_ext:extension_same -> bool -> unit
type of functions that register new ACSL extensions to be used in place of various kinds of ACSL annotations.
The labelled parameter plugin
is used to specify which plugin registers this new extension. It can be used, together with the syntax \plugin::name _
in ACSL annotations (instead of just name _
), to do some verifications and get better warnings/errors messages.
The optional preprocessor
is a function to be applied by the parser on the untyped content of the extension before parsing the rest of the processed file. By default, this function is the identity.
The typer
is applied when transforming the untyped AST to Cil. It recieves the typing context of the annotation that can be used to type the received logic expressions (see Logic_typing.typing_context
), and the location of the annotation.
The optional visitor
allows changing the way the ACSL extension is visited. By default, the behavior is Cil.DoChildren
, which ends up visiting each identified predicate/term in the list and leave the id as is.
The optional printer
allows changing the way the ACSL extension is pretty printed. By default, it prints the name of the extension followed by the formatted predicates, terms or identifier according to the Cil_types.acsl_extension_kind
.
The optional short_printer
allows changing the Printer.pp_short_extended
behavior for the ACSL extension. By default, it just prints the name
. It is for example used for the filetree in the GUI.
The optional is_same_ext
parameter allows checking whether two versions of the extended annotation are identical or not during a run of Ast_diff.compare_ast
. By default, Ast_diff
will compare the lists of terms/predicates.
The status
indicates whether the extension can be assigned a property status or not.
Here is a basic example:
let count = ref 0
let foo_typer ctxt loc = function
| [] ->
let id = !count in incr count;
Ext_id id
| [p] ->
Ext_preds [ctxt.type_predicate ctxt (ctxt.post_state [Normal]) p]
| _ ->
typing_context.error loc "expecting a predicate after keyword FOO"
let () =
Acsl_extension.register_behavior ~plugin:"myplugin" "FOO" foo_typer false
type register_extension_block = plugin:string -> string -> ?preprocessor:extension_preprocessor_block -> extension_typer_block -> ?visitor:extension_visitor -> ?printer:extension_printer -> ?short_printer:extension_printer -> ?is_same_ext:extension_same -> bool -> unit
same as register_extension
, but for extensions that parse an axiomatic block, resulting in a Cil_types.acsl_extension_kind.Ext_annot
.
val register_behavior : register_extension
Register a behavior extension, i.e. new clauses of contracts
val register_global : register_extension
Register extension for global annotation.
val register_global_block : register_extension_block
Registers extension for global block annotation.
val register_code_annot : register_extension
Registers extension for code annotation to be evaluated at _current_ program point.
val register_code_annot_next_stmt : register_extension
Registers extension for code annotation to be evaluated for the _next_ statement.
val register_code_annot_next_loop : register_extension
Registers extension for loop annotation.
val register_code_annot_next_both : register_extension
Registers extension both for code and loop annotations.
val register_module_importer : plugin:string -> string -> extension_module_importer -> unit
Module importer extensions allow extending the import clause with external loaders. For instance, consider the following declaration:
//@ import \myplugin::A: foo::bar;
This import clause will invoke an external module importer named "A"
provided it has been properly registered by plugin myplugin
.
A module importer extension is a function that receives a module_builder
parameter to be populated with contents of the module. The module name is provided as list (See Logic_utils.longident
for details).
New type and function symbols shall be created with `Cil.make_xxx` functions. The registered symbols will be automatically prefixed with the name of the imported module if necessary.
The register module importer function might be invoked several times, typically when a given module is imported from several files. Although external module importers might use memoization internally, the provided module builder shall be populated on every call.