Memory-managed wrapper type.

Compares the two Bytes values.

This function can be used to sort GBytes instances in lexicographical order.

If bytes1 and bytes2 have different length but the shorter one is a prefix of the longer one then the shorter one is considered to be less than the longer one. Otherwise the first byte where both differ is used for comparison. If bytes1 has a smaller value at that position it is considered less, otherwise greater than bytes2.

Since: 2.32

Compares the two Bytes values being pointed to and returns TRUE if they are equal.

This function can be passed to GHashTable.new() as the keyEqualFunc parameter, when using non-NULL GBytes pointers as keys in a GHashTable.

Since: 2.32

Get the byte data in the Bytes.

This data should not be modified.

This function will always return the same pointer for a given GBytes.

NULL may be returned if size is 0. This is not guaranteed, as the GBytes may represent an empty string with data non-NULL and size as 0. NULL will not be returned if size is non-zero.

Since: 2.32

Gets a pointer to a region in bytes.

The region starts at offset many bytes from the start of the data and contains nElements many elements of elementSize size.

nElements may be zero, but elementSize must always be non-zero. Ideally, elementSize is a static constant (eg: sizeof a struct).

This function does careful bounds checking (including checking for arithmetic overflows) and returns a non-NULL pointer if the specified region lies entirely within the bytes. If the region is in some way out of range, or if an overflow has occurred, then NULL is returned.

Note: it is possible to have a valid zero-size region. In this case, the returned pointer will be equal to the base pointer of the data of bytes, plus offset. This will be non-NULL except for the case where bytes itself was a zero-sized region. Since it is unlikely that you will be using this function to check for a zero-sized region in a zero-sized bytes, NULL effectively always means ‘error’.

Since: 2.70

Get the size of the byte data in the Bytes.

This function will always return the same value for a given GBytes.

Since: 2.32

Creates an integer hash code for the byte data in the Bytes.

This function can be passed to GHashTable.new() as the keyHashFunc parameter, when using non-NULL GBytes pointers as keys in a GHashTable.

Since: 2.32

Creates a new Bytes from data.

data is copied. If size is 0, data may be NULL.

As an optimization, bytesNew may avoid an extra allocation by copying the data within the resulting bytes structure if sufficiently small (since GLib 2.84).

Since: 2.32

Creates a Bytes which is a subsection of another GBytes.

The offset + length may not be longer than the size of bytes.

A reference to bytes will be held by the newly created GBytes until the byte data is no longer needed.

Since 2.56, if offset is 0 and length matches the size of bytes, then bytes will be returned with the reference count incremented by 1. If bytes is a slice of another GBytes, then the resulting GBytes will reference the same GBytes instead of bytes. This allows consumers to simplify the usage of GBytes when asynchronously writing to streams.

Since: 2.32

Creates a new Bytes from data.

After this call, data belongs to the GBytes and may no longer be modified by the caller. The memory of data has to be dynamically allocated and will eventually be freed with free.

For creating GBytes with memory from other allocators, see Bytes.new_with_free_func().

data may be NULL if size is 0.

Since: 2.32

Increase the reference count on bytes.

Since: 2.32

Releases a reference on bytes.

This may result in the bytes being freed. If bytes is NULL, it will return immediately.

Since: 2.32

Unreferences the bytes, and returns a new mutable ByteArray containing the same byte data.

As an optimization, the byte data is transferred to the array without copying if this was the last reference to bytes and bytes was created with bytesNew, bytesNewTake or byteArrayFreeToBytes and the buffer was larger than the size Bytes may internalize within its allocation. In all other cases the data is copied.

Do not use it if bytes contains more than G_MAXUINT bytes. ByteArray stores the length of its data in guint, which may be shorter than gsize, that bytes is using.

Since: 2.32

Unreferences the bytes, and returns a pointer the same byte data contents.

As an optimization, the byte data is returned without copying if this was the last reference to bytes and bytes was created with bytesNew, bytesNewTake or byteArrayFreeToBytes and the buffer was larger than the size Bytes may internalize within its allocation. In all other cases the data is copied.

Since: 2.32