package b0
Software construction and deployment kit
Install
Dune Dependency
Authors
Maintainers
Sources
b0-0.0.1.tbz
sha256=dba2fc571f39f3b8e87ee55c77bdec7ec6a5ddc7d99b8b20aeda848af546be04
md5=51ee1d66acc4d7f87bdceac1341b7711
doc/b00_kit/B00_ocaml/Lib_name/index.html
Module B00_ocaml.Lib_name
Library names
Module names
The type for library names looked up in OCAMLPATH
.
This is either:
- The name of an OCaml library that follows the OCaml library convention. For example the
b0.std
names looks upb0/std/lib.cm{a,xa,xs}
. These libraries are assumed to have been compiled according to the library convention and have their library dependencies embedded in their objects. - For legacy reasons, the name of an OCaml library followed by a slash to indicate the name of an archive. That is for example
b0.std/b0_std
, which looks upb0/std/b0_std.cm{a,xa,xs}
. These libraries do not have their library dependencies specified, their dependencies are looked by a best-effort data-driven resolution procedure.
val v : string -> t
v s
is a library for n
. Raises Invalid_argument
if s
is not a valid library name.
val of_string : string -> (t, string) Stdlib.result
of_string s
is a library name from n
.
val to_string : ?no_legacy:bool -> t -> string
to_string n
is n
as a string. If no_legacy
is true does not show the legacy part of the lib.
val is_legacy : t -> bool
legacy n
is true
if n
is a legacy name.
val pp : t B00_std.Fmt.t
pp
formats a library name.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>
On This Page