[PATCH 3/3] rbtree: Do not set node off-tree in extract
Sebastian Huber
sebastian.huber at embedded-brains.de
Mon Jul 21 17:54:08 UTC 2014
On 07/21/2014 07:23 PM, Joel Sherrill wrote:
> Unless the chain has changed to have the property of
> "dangerous to extract if not on", this should be OK.
>
> My thinking is that higher level code would be checking a state
> of some sort and know whether to extract from the underlying
> chain or rbtree container.
>
> Is this true? If so, this looks OK.
Yes, this is analogous to the chains. The lowest level implementation
should not do consistency checks (except via _Assert()).
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel
mailing list