bin_dump ?header writer v uses writer to first compute the size of
v in the binary protocol, then allocates a buffer of exactly this
size, and then writes out the value.
bin_read_stream ?max_size ~read reader reads binary protocol data
from a stream as generated by the read function, which places
data of a given length into a given buffer.
blit_buf ?src_pos ~src ?dst_pos ~dst len blits len bytes of the
source buffer src starting at position src_pos to destination
buffer dst starting at position dst_pos.
blit_buf_string ?src_pos src ?dst_pos dst ~len blits len
bytes of the source buffer src starting at position src_pos
to string dst starting at position dst_pos.
blit_string_buf ?src_pos src ?dst_pos dst ~len blits len
bytes of the source string src starting at position src_pos
to buffer dst starting at position dst_pos.
make1 mk_c_reader ml_el_reader takes a higher-order C-style reader
mk_c_reader and an ML-reader ml_el_reader that operates on the
same type as the argument of the C-style reader.
make1 mk_c_writer ml_el_writer takes a higher-order C-style writer
mk_c_writer and an ML-writer ml_el_writer that operates on the
same type as the argument of the C-style writer.
make3 mk_c_reader ml_el1_reader ml_el2_reader ml_el3_reader like
Read_c.make1 but operates on unsafe C-style write functions for types
with three type parameters.
make3 mk_c_writer ml_el1_writer ml_el2_writer ml_el3_writer like
Write_c.make1 but operates on unsafe C-style write functions for types
with three type parameters.