This module provides functions to encode arbitrary data structures as sequences of bytes, which can then be written on a file or sent over a pipe or network connection. The bytes can then be read back later, possibly in another process, and decoded back into a data structure. The format for the byte sequences is compatible across all machines for a given version of OCaml.
Warning: marshaling is currently not type-safe. The type
of marshaled data is not transmitted along the value of the data,
making it impossible to check that the data read back possesses the
type expected by the context. In particular, the result type of
Marshal.from_* functions is given as
'a, but this is
misleading: the returned OCaml value does not possess type
'a; it has one, unique type which cannot be determined
at compile-type. The programmer should explicitly give the expected
type of the returned value, using the following syntax:
(Marshal.from_channel chan : type). Anything can happen at run-time if the object in the file does not belong to the given type.
Marshal.inputmust be opened in binary mode, using e.g.
BatPervasives.open_in_bin; channels opened in text mode will cause unmarshaling errors on platforms where text channels behave differently than binary channels, e.g. Windows.
Don't preserve sharing
Send function closures
Ensure 32-bit compatibility
val output :
'b BatInnerIO.output -> ?sharing:bool -> ?closures:bool -> 'a -> unit
output out vwrites the representation of
true(default value), circularities and sharing inside the value
vare detected and preserved in the sequence of bytes produced. In particular, this guarantees that marshaling always terminates. Sharing between values marshaled by successive calls to
outputis not detected, though. If
false, sharing is ignored. This results in faster marshaling if
vcontains no shared substructures, but may cause slower marshaling and larger byte representations if
vactually contains sharing, or even non-termination if
false(default value) marshaling fails when it encounters a functional value inside
v: only ``pure'' data structures, containing neither functions nor objects, can safely be transmitted between different programs. If
true, functional values will be marshaled as a position in the code of the program. In this case, the output of marshaling can only be read back in processes that run exactly the same program, with exactly the same compiled code. (This is checked at un-marshaling time, using an MD5 digest of the code transmitted along with the code position.)
val to_bytes :
'a -> extern_flags list -> Bytes.t
Marshal.to_bytes v flagsreturns a byte sequence containing the representation of
flagsargument has the same meaning as for
val to_string :
'a -> extern_flags list -> string
to_bytesbut return the result as a string instead of a byte sequence.
val to_buffer :
Bytes.t -> int -> int -> 'a -> extern_flags list -> int
Marshal.to_buffer buff ofs len v flagsmarshals the value
v, storing its byte representation in the sequence
buff, starting at index
ofs, and writing at most
lenbytes. It returns the number of bytes actually written to the sequence. If the byte representation of
vdoes not fit in
lencharacters, the exception
val input :
BatInnerIO.input -> 'a
input inpreads from
inpthe byte representation of a structured value, as produced by one of the
Marshal.to_*functions, and reconstructs and returns the corresponding value.
val from_bytes :
Bytes.t -> int -> 'a
Marshal.from_bytes buff ofsunmarshals a structured value like
Marshal.from_channeldoes, except that the byte representation is not read from a channel, but taken from the byte sequence
buff, starting at position
ofs. The byte sequence is not mutated.
val from_string :
string -> int -> 'a
from_bytesbut take a string as argument instead of a byte sequence.
val header_size :
Marshal.header_sizeis the size, in bytes, of the header.
buff ofsis the size, in bytes, of the data part, assuming a valid header is stored in
buffstarting at position
buff ofsis the total size, in bytes, of the marshaled value. Both
ofsdoes not contain a valid header.
To read the byte representation of a marshaled value into
a byte sequence, the program needs to read first
Marshal.header_size bytes into the sequence,
then determine the length of the remainder of the
make sure the sequence is large enough to hold the remaining
data, then read it, and finally call
to unmarshal the value.
val data_size :
Bytes.t -> int -> int
val total_size :
Bytes.t -> int -> int
val to_channel :
'b BatInnerIO.output -> 'a -> extern_flags list -> unit
val from_channel :
BatInnerIO.input -> 'a