TDELETE(3POSIX)
๐ TDELETE(3POSIX) ๐ โ POSIX Programmer's Manual
โจ PROLOG โจ
okay so real talk first: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. so if you're on Linux, double-check before you go feral with it. ๐
๐ NAME ๐
tdelete, tfind, tsearch, twalk โ manage a binary search tree
๐ฆ SYNOPSIS ๐ฆ
#include <search.h>
void *tdelete(const void *restrict key, void **restrict rootp,
int(*compar)(const void *, const void *));
void *tfind(const void *key, void *const *rootp,
int(*compar)(const void *, const void *));
void *tsearch(const void *key, void **rootp,
int (*compar)(const void *, const void *));
void twalk(const void *root,
void (*action)(const void *, VISIT, int));
๐ธ DESCRIPTION ๐ธ
So like, tdelete(), tfind(), tsearch(), and twalk() are the four functions that manipulate binary search trees. Comparisons? You bring your own routine, bestie, and its address gets passed as the compar argument. That routine gets called with two arguments, which are pointers to the elements being compared. Your application shall ensure that the user-supplied routine returns an integer less than, equal to, or greater than 0, depending on whether the first argument is considered less than, equal to, or greater than the second argument. And no, the comparison function doesn't have to compare every byte, so arbitrary data may be contained in the elements in addition to the values being compared. โจ
tsearch() is the one that builds and accesses the tree. The key argument is a pointer to an element to be accessed or stored. If there's a node in the tree whose element is equal to the value pointed to by key, a pointer to this found node shall be returned. Otherwise, the value pointed to by key shall be inserted (that is, a new node is created and the value of key is copied to this node), and a pointer to this node returned. Only pointers are copied, so the application shall ensure that the calling routine stores the data. The rootp argument points to a variable that points to the root node of the tree. A null pointer value for the variable pointed to by rootp denotes an empty tree; in this case, the variable shall be set to point to the node which shall be at the root of the new tree.
Like tsearch(), tfind() shall search for a node in the tree, returning a pointer to it if found. But if it's not found, tfind() shall return a null pointer. The arguments for tfind() are the same as for tsearch().
tdelete() shall delete a node from a binary search tree. The arguments are the same as for tsearch(). The variable pointed to by rootp shall be changed if the deleted node was the root of the tree. If the deleted node was the root of the tree and had no children, the variable pointed to by rootp shall be set to a null pointer. The tdelete() function shall return a pointer to the parent of the deleted node, or an unspecified non-null pointer if the deleted node was the root node, or a null pointer if the node is not found.
๐จ bestie, listen: iftsearch()adds an element to a tree, ortdelete()successfully deletes an element from a tree, then concurrent use of that tree in another thread, or use of pointers produced by a previous call totfind()ortsearch(), produces undefined results. not "maybe weird", not "probably fine" โ undefined. periodt.
twalk() shall traverse a binary search tree. The root argument is a pointer to the root node of the tree to be traversed. (Any node in a tree may be used as the root for a walk below that node.) The action argument is the name of a routine to be invoked at each node. This routine is, in turn, called with three arguments. The first argument shall be the address of the node being visited. The structure pointed to by this argument is unspecified and shall not be modified by the application, but it shall be possible to cast a pointer-to-node into a pointer-to-pointer-to-element to access the element stored in the node. The second argument shall be a value from an enumeration data type:
typedef enum { preorder, postorder, endorder, leaf } VISIT;
(defined in <search.h>), depending on whether this is the first, second, or third time that the node is visited (during a depth-first, left-to-right traversal of the tree), or whether the node is a leaf. The third argument shall be the level of the node in the tree, with the root being level 0.
If the calling function alters the pointer to the root, the result is undefined.
If the functions pointed to by action or compar (for any of these binary search functions) change the tree, the results are undefined.
These functions are thread-safe only as long as multiple threads do not access the same tree. so like, don't share the tree across threads and expect magic. ๐
๐ RETURN VALUE ๐
If the node is found, both tsearch() and tfind() shall return a pointer to it. If not, tfind() shall return a null pointer, and tsearch() shall return a pointer to the inserted item.
A null pointer shall be returned by tsearch() if there is not enough space available to create a new node.
A null pointer shall be returned by tdelete(), tfind(), and tsearch() if rootp is a null pointer on entry.
The tdelete() function shall return a pointer to the parent of the deleted node, or an unspecified non-null pointer if the deleted node was the root node, or a null pointer if the node is not found.
The twalk() function shall not return a value.
๐จ ERRORS ๐จ
No errors are defined.
The following sections are informative.
๐ EXAMPLES ๐
The following code reads in strings and stores structures containing a pointer to each string and a count of its length. It then walks the tree, printing out the stored strings and their lengths in alphabetical order.
#include <limits.h>
#include <search.h>
#include <stdlib.h>
#include <string.h>
#include <stdio.h>
struct element { /* Pointers to these are stored in the tree. */
int count;
char string[];
};
void *root = NULL; /* This points to the root. */
int main(void)
{
char str[_POSIX2_LINE_MAX+1];
int length = 0;
struct element *elementptr;
void *node;
void print_node(const void *, VISIT, int);
int node_compare(const void *, const void *),
delete_root(const void *, const void *);
while (fgets(str, sizeof(str), stdin)) {
/* Set element. */
length = strlen(str);
if (str[length-1] == '\n')
str[--length] = '\0';
elementptr = malloc(sizeof(struct element) + length + 1);
strcpy(elementptr->string, str);
elementptr->count = 1;
/* Put element into the tree. */
node = tsearch((void *)elementptr, &root, node_compare);
if (node == NULL) {
fprintf(stderr,
"tsearch: Not enough space available\n");
exit(EXIT_FAILURE);
}
else if (*(struct element **)node != elementptr) {
/* A node containing the element already exists */
(*(struct element **)node)->count++;
free(elementptr);
}
}
twalk(root, print_node);
/* Delete all nodes in the tree */
while (root != NULL) {
elementptr = *(struct element **)root;
printf("deleting node: string = %s, count = %d\n",
elementptr->string,
elementptr->count);
tdelete((void *)elementptr, &root, delete_root);
free(elementptr);
}
return 0;
}
/*
* This routine compares two nodes, based on an
* alphabetical ordering of the string field.
*/
int
node_compare(const void *node1, const void *node2)
{
return strcmp(((const struct element *) node1)->string,
((const struct element *) node2)->string);
}
/*
* This comparison routine can be used with tdelete()
* when explicitly deleting a root node, as no comparison
* is necessary.
*/
int
delete_root(const void *node1, const void *node2)
{
return 0;
}
/*
* This routine prints out a node, the second time
* twalk encounters it or if it is a leaf.
*/
void
print_node(const void *ptr, VISIT order, int level)
{
const struct element *p = *(const struct element **) ptr;
if (order == postorder || order == leaf) {
(void) printf("string = %s, count = %d\n",
p->string, p->count);
}
}
๐ง APPLICATION USAGE ๐ง
The root argument to twalk() is one level of indirection less than the rootp arguments to tdelete() and tsearch().
There are two nomenclatures used to refer to the order in which tree nodes are visited. The twalk() function uses preorder, postorder, and endorder to refer respectively to visiting a node before any of its children, after its left child and before its right, and after both its children. The alternative nomenclature uses preorder, inorder, and postorder to refer to the same visits, which could result in some confusion over the meaning of postorder. so yes, the postorder name is a whole vibe check trap. iykyk.
Since the return value of tdelete() is an unspecified non-null pointer in the case that the root of the tree has been deleted, applications should only use the return value of tdelete() as indication of success or failure and should not assume it can be dereferenced. Some implementations in this case will return a pointer to the new root of the tree (or to an empty tree if the deleted root node was the only node in the tree); other implementations return arbitrary non-null pointers.
๐ญ RATIONALE ๐ญ
None.
๐ฎ FUTURE DIRECTIONS ๐ฎ
None.
๐ SEE ALSO ๐
hcreate(), lsearch()
The Base Definitions volume of POSIX.1โ2017, <search.h>
๐ COPYRIGHT ๐
okay bestie, this is the boring-but-important part, the receipts section, the "who actually wrote this" moment, and ngl you do need to read it ๐
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group.
fr fr, if there's ever any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. Like, that one wins, no debate, periodt ๐
The original Standard can be obtained online at:
http://www.opengroup.org/unix/online.html
๐ a lil disclaimer about typos
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see:
https://www.kernel.org/doc/man-pages/reporting_bugs.html
like, not me being the messenger here, but if something looks cursed, it's probably a conversion oopsie, not the actual standard ๐ so go snitch on it at that link and the maintainers will handle it ๐ซถ
and that's the whole page, bestie!! you made it to the end ๐ this one's from IEEE/The Open Group, dated 2017, and it's the TDELETE(3POSIX) page โ go forth and delete those timeouts responsibly โจ๐ฆ๐
๐ฆ where this page comes from
- debian bookworm: manpages-posix-dev 2017a-2 ยท Other
- debian trixie: manpages-posix-dev 2017a-2 ยท Other
- ubuntu jammy: manpages-posix-dev 2017a-2 ยท Other
- ubuntu noble: manpages-posix-dev 2017a-2 ยท Other
- ubuntu resolute: manpages-posix-dev 2017a-2build1 ยท Other
- ubuntu stonking: manpages-posix-dev 2017a-2.1 ยท Other
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms