there are two proposals floatingat the moment.. 1/ I added debugging stuff to TAILQ to help find bad usages in KSE. Qusetion/proposal: Should I extend this to other types and add it to the file (or not delete what is there now)
2/ We could add a new macro/method that is slightly less efficient than the current FOREACH macros, but allows element removal. Exisiting methods would no change. On Thu, 4 Jul 2002, Daniel Eischen wrote: > On Thu, 4 Jul 2002, Julian Elischer wrote: > > that was teh plan... we're just discussing the name.. > > TAILQ_FOREACH_SAFE ? > > Oh, I thought the initial proposal was to add a _new_ interface > that allowed safe removals while traversing the list (and allow > the existing macros to be changed for debugging purposes/extra > sanity checks). > > -- > Dan Eischen > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
