Gathering some basic internal info

Author(s): Daniel Cabeza, Manuel Carro.

Version: 1.5#118 (2000/4/19, 18:13:43 CEST)

Version of last change: 1.3#13 (1999/7/2, 18:49:49 MEST)

............... In development ...............

• Usage and interface (system_info)
• Documentation on exports (system_info)
• Documentation on internals (system_info)

Usage and interface (system_info)

Documentation on exports (system_info)

PREDICATE: get_arch/1:

This predicate will describe the computer architecture wich is currently executing the predicate.

Computer architectures are identified by a simple atom. This atom is implementation-defined, and may suffer any change from one Ciao Prolog version to another.

For example,Ciao Prolog running on an Intel-based machine will retrieve:

?- get_arch(I).

I = i86 ? ;

no
?- 

Usage 1: get_arch(?(ArchDescriptor))

• Description: Unifies ArchDescriptor with a simple atom which describes the computer architecture currently executing the predicate.
• Calls should, and exit will be compatible with: ?(ArchDescriptor) is an atom. (basic_props:atm/1)

Usage 2: get_arch(ArchDescriptor)

• Description: Unifies ArchDescriptor with a simple atom which describes the computer architecture currently executing the predicate.
• Calls should, and exit will be compatible with: ArchDescriptor is an atom. (basic_props:atm/1)

PREDICATE: get_os/1:

This predicate will describe the Operating System which is running on the machine currently executing the Prolog program.

Operating Systems are identified by a simple atom. This atom is implementation-defined, and may suffer any change from one Ciao Prolog version to another.

For example,Ciao Prolog running on Linux will retrieve:

?- get_os(I).

I = 'LINUX' ? ;

no
?- 

Usage 1: get_os(?(OsDescriptor))

• Description: Unifies OsDescriptor with a simple atom which describes the running Operating System when predicate was called.
• Calls should, and exit will be compatible with: ?(OsDescriptor) is an atom. (basic_props:atm/1)

Usage 2: get_os(OsDescriptor)

• Description: Unifies OsDescriptor with a simple atom which describes the running Operating System when predicate was called.
• Calls should, and exit will be compatible with: OsDescriptor is an atom. (basic_props:atm/1)

PREDICATE: this_module/1:

Meta-predicate with arguments: this_module(addmodule).

Usage 1:

• Description: Module is the internal module identifier for current module.
• Call and exit should be compatible with: Arg1 is an internal module identifier (system_info:internal_module_id/1)

Usage 2:

• Description: Module is the internal module identifier for current module.
• Call and exit should be compatible with: Arg1 is an internal module identifier (system_info:internal_module_id/1)

PREDICATE: current_module/1:

This predicate will successively unify its argument with all module names currently loaded. Module names will be simple atoms.

When called using a free variable as argument, it will retrieve on backtracking all modules currently loaded. This is usefull when called from the Ciao toplevel.

When called using a module name as argument it will check whether the given module is loaded or not. This is usefull when called from user programs.

Usage 1: current_module(Module)

• Description: Retrieves (on backtracking) all currently loaded modules into your application.
• Call and exit should be compatible with: Module is an atom. (basic_props:atm/1)

Usage 2: current_module(Module)

• Description: Retrieves (on backtracking) all currently loaded modules into your application.
• Call and exit should be compatible with: Module is an atom. (basic_props:atm/1)

PREDICATE: ciaolibdir/1:

Usage 1: ciaolibdir(CiaoPath)

• Description: CiaoPath is the path to the root of the Ciao libraries. Inside this directory, there are the directories 'lib', 'library' and 'contrib', which contain library modules.
• Call and exit should be compatible with: CiaoPath is an atom. (basic_props:atm/1)

Usage 2: ciaolibdir(CiaoPath)

• Description: CiaoPath is the path to the root of the Ciao libraries. Inside this directory, there are the directories 'lib', 'library' and 'contrib', which contain library modules.
• Call and exit should be compatible with: CiaoPath is an atom. (basic_props:atm/1)

Documentation on internals (system_info)

PROPERTY: internal_module_id/1:

For a user file it is a term user/1 with an argument different for each user file, for other modules is just the name of the module (as an atom).

Usage: internal_module_id(M)

• Description: M is an internal module identifier

Go to the first, previous, next, last section, table of contents.