Module System
Coqtop specific system utilities
Directories
type unix_path= stringtype file_kind=|FileDir of unix_path * string|FileRegular of string
val exclude_directory : unix_path -> unit
Files and load paths
val all_subdirs : unix_path:string -> (CUnix.physical_path * string list) listval is_in_path : CUnix.load_path -> string -> boolval is_in_system_path : string -> boolval where_in_path : ?warn:bool -> CUnix.load_path -> string -> CUnix.physical_path * stringval find_file_in_path : ?warn:bool -> CUnix.load_path -> string -> CUnix.physical_path * stringval trust_file_cache : bool Stdlib.reftrust_file_cacheindicates whether we trust the underlying mapped file-system not to change along the execution of Coq. This assumption greatly speds up file search, but it is often inconvenient in interactive mode
I/O functions
exceptionBad_magic_number of magic_number_errorexceptionBad_version_number of magic_number_error
Time stamps.
val fmt_time_difference : time -> time -> Pp.tval with_time : batch:bool -> header:Pp.t -> ('a -> 'b) -> 'a -> 'bval get_toplevel_path : ?byte:bool -> string -> stringget_toplevel_path programbuilds a complete path to the executable denoted byprogram. This involves:- locating the directory: we don't rely on PATH as to make calls to /foo/bin/coqtop chose the right /foo/bin/coqproofworker
- adding the proper suffixes: .opt/.byte depending on the current mode, + .exe if in windows.
Note that this function doesn't check that the executable actually exists. This is left back to caller, as well as the choice of fallback strategy. We could add a fallback strategy here but it is better not to as in most cases if this function fails to construct the right name you want you execution to fail rather than fall into choosing some random binary from the system-wide installation of Coq.