List Interface
The list.h
header defines a common interface for all list implementations.
UCX already comes with two common list implementations (linked list and array list) that should cover most use cases. But if you feel the need to implement an own list, you will find instructions below.
The function cxLinkedListCreate()
creates a new linked list with the specified allocator
which stores elements of size elem_size
. The elements are supposed to be compared with the specified comparator
(cf. Access and Find). The function cxLinkedListCreateSimple()
will use the stdlib default allocator and does not specify a compare function.
Array lists can be created with cxArrayListCreate()
where the additional argument initial_capacity
specifies for how many elements the underlying array shall be initially allocated.
If CX_STORE_POINTERS
is used as elem_size
, the actual element size will be sizeof(void*)
and the list will behave slightly differently when accessing elements. Lists that are storing pointers will always return the stored pointer directly, instead of returning a pointer into the list's memory, thus saving you from unnecessary dereferencing. Conversely, when adding elements to the list, the pointers you specify (e.g. in cxListAdd()
or cxListInsert()
) are directly added to the list, instead of copying the contents pointed to by the argument.
Example
In the following example we create a linked-list of regular expressions for filtering data.
If in the above example the list was created with CX_STORE_POINTERS
instead of sizeof(regex_t)
, the add_pattern()
function would need to be changed as follows:
Also, just registering regfree()
as destructor is not sufficient anymore, because the regex_t
structure also needs to be freed. Therefore, we would need to wrap the calls to regfree()
and free()
into an own destructor, which we then register with the list. However, it should be clear by now that using CX_STORE_POINTERS
is a bad choice for this use case to begin with.
As a rule of thumb: if you allocate memory for an element that you immediately put into the list, consider storing the element directly. And if you are getting pointers to already allocated memory from somewhere else, and you just want to organize those elements in a list, then consider using CX_STORE_POINTERS
.
Insert
The function cxListAdd()
appends the element elem
to the list and returns zero on success or non-zero when allocating the memory for the element fails. Similarly, cxListInsert()
adds the element at the specified index
, and cxListInsertSorted()
adds the element at the correct position so that the list remains sorted according to the list's compare function.
When you are currently iterating through a list, you can insert elements before or after the current position of the iterator with cxListInsertBefore()
or cxListInsertAfter()
, respectively. This should be done with mutating iterators only, but is also defined for normal iterators.
If the list is storing pointers (cf. cxCollectionStoresPointers()
), the pointer elem
is directly added to the list. Otherwise, the contents at the location pointed to by elem
are copied to the list's memory with the element size specified during creation of the list.
On the other hand the array
argument for cxListAddArray()
, cxListInsertArray()
, and cxListInsertSortedArray()
must always point to an array of elements to be added (i.e. either an array of pointers, or an array of actual elements).
A special requirement for cxListInsertSortedArray()
is, that the array
must already be sorted.
Access and Find
The function cxListAt()
accesses the element at the specified index
. If the list is storing pointers (i.e. cxCollectionStoresPointers()
returns true
), the pointer at the specified index is directly returned. Otherwise, a pointer to element at the specified index is returned. If the index is out-of-bounds, the function returns NULL
.
On the other hand, cxListFind()
searches for the element pointed to by elem
by comparing each element in the list with the list`s compare function, and returns the first index when the element was found. Otherwise, the function returns the list size.
The function cxListFindRemove()
behaves like cxListFind()
, except that it also removes the first occurrence of the element from the list. This will also call destructor functions, if specified, so take special care when you continue to use elem
, or when the list is storing pointers and the element appears more than once in the list.
With cxListIndexValid()
you can check the index returned by cxListFind()
or cxListFindRemove()
, which is more convenient than comparing the return value if the return value of cxListSize()
.
Remove
The function cxListRemove()
removes the element at the specified index and returns zero, or returns non-zero if the index is out-of-bounds. The function cxListRemoveArray()
removes num
elements starting at index
and returns the number of elements that have been removed. For each removed element, the destructor functions are called.
On the other hand, cxListRemoveAndGet()
and cxListRemoveArrayAndGet()
do not invoke the destructor functions and instead copy the elements into the targetbuf
, which must be large enough to hold the removed elements.
The function cxListFindRemove()
finds the first element within the list that is equivalent to the element pointed to by elem
and removes it from the list. This will also call destructor functions, if specified, so take special care when you continue to use elem
.
The function cxListClear()
simply removes all elements from the list, invoking the destructor functions. It behaves equivalently, but is usually more efficient than calling cxListRemove()
for every index.
Iterators
The functions cxListIterator()
and cxListBackwardsIterator()
create iterators that start and the first or the last element in the list and iterate through the entire list.
The functions cxListIteratorAt()
and cxListBackwardsIteratorAt()
start with the element at the specified index and iterate until the end, or the beginning of the list, respectively.
The functions with Mut
in are equivalently, except that they create a mutating iterator. Removing elements via a mutating iterator will cause an invocation of the destructor functions for the removed element.
If is safe to specify an out-of-bounds index in which case an iterator is returned for which cxIteratorValid()
returns false
, immediately.
Reorder
The function cxListSwap()
swaps two elements specified by the indices i
and j
. The return value is non-zero if one of the indices is out-of-bounds.
The function cxListReverse()
reorders all elements, so that they appear in exactly the opposite order after invoking this function.
The function cxListSort()
sorts all elements with respect to the list's compare function, unless the list is already sorted (cf. cxCollectionSorted()
), in which case the function immediately returns.
Default UCX implementations of the list interface make use of small buffer optimizations when swapping elements.
Compare
Arbitrary lists can be compared element-wise with cxListCompare()
, as long as the compare functions of both lists are equivalent.
That means, you can compare an UCX array list with a linked list, and you could even compare lists that are storing pointers with lists that are not storing pointers.
However, the optimized list-internal compare implementation is only used, when both the compare functions and the list classes are identical. Otherwise, cxListCompare()
will behave as if you were iterating through both lists and manually comparing the elements.
The return value of cxListCompare()
is zero, if the lists are element-wise equivalent. If they are not, the non-zero return value equals the return value of the used compare function for the first pair of elements that are not equal.
Dispose
No matter with which function a CxList
has been created, you can always deallocate the entire memory with a call to cxListFree()
.
The effect is equivalent to invoking cxListClear()
plus deallocating the memory for the list structure. That means, for each element in the list, the destructor functions are called before deallocating the list.
When the list has been storing pointers, make sure that either another reference to the same memory exist in your program, or any of the destructor functions deallocates the memory. Otherwise, there is a risk of a memory leak.
Implement own List Structures
If you want to create your own list implementation, this is extremely easy.
You just need to define a function for creating your list and assign a cx_list_class
structure with the pointers to your implementation. Then you call the cx_list_init()
helper function to initialize the collection sture. This also automatically adds support for CX_STORE_POINTERS
to your list.
The required behavior for the implementations is described in the following table. You can always look at the source code of the UCX implementations to get inspiration.
Function | Description |
---|---|
| Invoke destructor functions on all elements and remove them from the list. |
| Invoke destructor functions on all elements and deallocate the entire list memory. |
| Insert a single element at the specified index. Return zero on success and non-zero on failure. |
| Insert an array of elements starting at the specified index. Return the number of elements inserted. |
| Insert an array of sorted elements into a sorted list. Return the number of elements inserted. |
| Insert a single element depending on the iterator position. The third argument to this function is zero when the element shall be inserted after the iterator position and non-zero if it shall be inserted before the iterator position. The implementation is also responsible for adjusting the iterator, respectively. |
| Removes a multiple elements starting at the specified index. If a target buffer is specified, copy the elements to that buffer. Otherwise, invoke the destructor functions for the elements. Return the number of elements actually removed. |
| Swap two elements by index. Return zero on success or non-zero when any index was out-of-bounds. |
| Return a pointer to the element at the specified index or |
| Search for the specified element with the list's compare function and return the index if found. If the |
| Sort all elements in the list with respect to the list's compare function. |
| Only function pointer that may be |
| Reorders all elements in the list so that they appear in exactly the opposite order. |
| Creates an iterator starting at the specified index. The Boolean argument indicates whether iteration is supposed to traverse backwards. |
Default Class Function Implementations
If you are satisfied with some of the default implementations, you can use some pre-defined functions. Note, however, that those are not optimized for any specific list structure and just serve as a quick and convenient solution if performance does not matter for your use case.
Default Function | Description |
---|---|
| Falls back to multiple calls of |
| Uses linear search to find insertion points. |
| Copies all elements to an array, applies |
| Uses a temporarily allocated buffer to perform a three-way-swap. |