package base_bigstring
- Types and exceptions
- Creation and string conversion
- Checking
- Accessors
- Blitting
- Search
-
Accessors for parsing binary values, analogous to
Binary_packing - 16-bit methods
- 32-bit methods
- 64-bit signed values
- 64-bit unsigned values
- 32-bit methods with full precision
- 64-bit methods with full precision
- String methods
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=0c77edb9db4f29797cd5c22dd07fdbe4ff668715be870b86dcc1d849730b8562
doc/base_bigstring/Base_bigstring/index.html
Module Base_bigstringSource
String type based on Bigarray, for use in I/O and C-bindings.
Types and exceptions
Type of bigstrings
Type of bigstrings which support hashing. Note that mutation invalidates previous hashes.
val hash_fold_t_frozen :
Ppx_hash_lib.Std.Hash.state ->
t_frozen ->
Ppx_hash_lib.Std.Hash.stateinclude Base.Equal.S with type t := t
Creation and string conversion
init n ~f creates a bigstring t of length n, with t.{i} = f i.
of_string ?pos ?len str
of_bytes ?pos ?len str
to_string ?pos ?len bstr
to_bytes ?pos ?len bstr
concat ?sep list returns the concatenation of list with sep in between each.
Checking
check_args ~loc ~pos ~len bstr checks the position and length arguments pos and len for bigstrings bstr.
get_opt_len bstr ~pos opt_len
Accessors
unsafe_get t pos returns the character at pos, without bounds checks.
unsafe_set t pos sets the character at pos, without bounds checks.
Blitting
blit ~src ?src_pos ?src_len ~dst ?dst_pos () blits src_len characters from src starting at position src_pos to dst at position dst_pos.
include Base.Blit.S with type t := t
memset t ~pos ~len c fills t with c within the range [pos, pos + len).
unsafe_memset t ~pos ~len c fills t with c within the range [pos, pos + len), without bounds checks.
Memcmp
memcmp t1 ~pos1 t2 ~pos2 ~len is like compare t1 t2 except performs the comparison on the subregions of t1 and t2 defined by pos1, pos2, and len.
val memcmp_bytes :
t ->
pos1:Base.int ->
Base.Bytes.t ->
pos2:Base.int ->
len:Base.int ->
Base.intmemcmp_bytes, for efficient memcmp between Bigstring and Bytes data.
val memcmp_string :
t ->
pos1:Base.int ->
Base.string ->
pos2:Base.int ->
len:Base.int ->
Base.intmemcmp_string, for efficient memcmp between Bigstring and string data.
Search
find ?pos ?len char t returns Some i for the smallest i >= pos such that t.{i} = char, or None if there is no such i.
Same as find, but does no bounds checking, and returns a negative value instead of None if char is not found.
val memmem :
haystack:t ->
needle:t ->
?haystack_pos:Base.int ->
?haystack_len:Base.int ->
?needle_pos:Base.int ->
?needle_len:Base.int ->
Base.unit ->
Base.int Base.optionSearch for the position of (a substring of) needle in (a substring of) haystack.
val unsafe_memmem :
haystack:t ->
needle:t ->
haystack_pos:Base.int ->
haystack_len:Base.int ->
needle_pos:Base.int ->
needle_len:Base.int ->
Base.intAs unsafe_find for memmem.
Accessors for parsing binary values, analogous to Binary_packing
These are in Bigstring rather than a separate module because:
1. Existing Binary_packing requires copies and does not work with bigstrings. 2. The accessors rely on the implementation of bigstring, and hence should change should the implementation of bigstring move away from Bigarray. 3. Bigstring already has some external C functions, so it didn't require many changes to the jbuild ^_^.
In a departure from Binary_packing, the naming conventions are chosen to be close to C99 stdint types, as it's a more standard description and it is somewhat useful in making compact macros for the implementations. The accessor names contain endian-ness to allow for branch-free implementations
<accessor> ::= <unsafe><operation><type><endian> <unsafe> ::= unsafe_ | '' <operation> ::= get_ | set_ <type> ::= int8 | uint8 | int16 | uint16 | int32 | uint32 | int64 | uint64 <endian> ::= _le | _be | ''
The unsafe_ prefix indicates that these functions do no bounds checking and silently truncate out-of-range numeric arguments.
16-bit methods
32-bit methods
Similar to the usage in binary_packing, the below methods are treating the value being read (or written), as an ocaml immediate integer, as such it is actually 63 bits. If the user is confident that the range of values used in practice will not require 64-bit precision (i.e. Less than Max_Long), then we can avoid allocation and use an immediate. If the user is wrong, an exception will be thrown (for get).
64-bit signed values
64-bit unsigned values
32-bit methods with full precision
64-bit methods with full precision
String methods
These are alternatives to to_string that follow the conventions of the int accessors, and in particular avoid optional arguments.
- Types and exceptions
- Creation and string conversion
- Checking
- Accessors
- Blitting
- Search
-
Accessors for parsing binary values, analogous to
Binary_packing - 16-bit methods
- 32-bit methods
- 64-bit signed values
- 64-bit unsigned values
- 32-bit methods with full precision
- 64-bit methods with full precision
- String methods