package conan
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=27974c6a24196088d9ec2a26e83d1e174a608a0745f68a435ebcd1abb22da385
sha512=58bd758ecb1d328fe25c141f4500eb6c14b2ffc1feee4a097b57ae48ab6eee1db8ea52cee06ba90fc06e03dba76e35465d8f38a5779040cb013f2b7367cc97ef
doc/conan.string/Conan_string/index.html
Module Conan_stringSource
recognition.
Conan_string is a system-free implementation of the file recognition. This implementation does not uses any syscalls - and it can be safely used into a MirageOS example.
So Conan_string does not have an access to a database. The user must rebuild a Conan.Tree.t by himself via tree_of_string for example. Then, from this tree, the user is able to recognize a payload as a simple string with run:
let v =
{file|0 byte 0x66
>1 byte 0x6f
>>1 byte 0x6f foo header
|file}
let tree = match Conan_string.tree_of_string v with
| Ok tree -> tree
| Error (`Msg err) -> failwith err
let database = Conan.Tree.database ~tree
let m = match Conan_string.run ~database contents with
| Ok m -> m
| Error (`Msg err) -> failwith errtree_of_string str tries to parse the given str as a decision tree according to the libmagic format.
val run :
database:Conan.Process.database ->
string ->
(Conan.Metadata.t, [> `Msg of string ]) resultrun ~database contents tries to recognize the given contents with the help of database. The databse can be made via Conan.Process.database. Indeed, a Conan.Tree.t can have some indirect decision paths so we must pre-process the tree to agglomerate such indirections.