Re: rb_tree_iterate(3) documentation vs. implementation

[David Young <dyoung%pobox.com@localhost>]

On Wed, Aug 29, 2012 at 09:11:34AM -0700, Jeff Rizzo wrote:
> On 8/28/12 11:12 AM, Paul Goyette wrote:
> >On Tue, 28 Aug 2012, Mindaugas Rasiukevicius wrote:
> >
> >>- There is also PR/45893.  The reason why these changes were not
> >>made are
> >> concerns about breaking backwards compatibility (apparently, there are
> >> 3rd party users of this library already).  In theory, it is not
> >>too late,
> >> as netbsd-6 will be the first release shipping rbtree(3), but
> >>we need to
> >> reach the consensus on this.
> >
> >Seems to me, we ought to get this "right" before we formally ship.
> >The "early adopters" who are already using rbtree(3) already
> >should be few in number and hopefully we could work with them to
> >adapt to the changes.
> >
> 
> Why is it that people still think that at this late date, we would
> entertain changing an API in NetBSD-6 when a release candidate is
> built and about to be announced?!?

I am opposed to delaying the release for this, myself.

In a subsequent release we can rename all of the rb_tree_*() routines
to rbtree_*().  The bad old rb_tree_iterate() can be a wrapper for
rbtree_iterate() that swaps RB_DIR_LEFT for RB_DIR_RIGHT (and vice
versa) when the 2nd argument is NULL.  Every other rb_tree_*() can be an
alias for the corresponding rbtree_*().  Or something like that.

Dave

-- 
David Young
dyoung%pobox.com@localhost    Urbana, IL    (217) 721-9981