On Tue, 24 Jun 2003, Joe Schaefer wrote: > However, I can see the value in not changing the current semantics > if people are concerned that the change may cause problems for third > party modules that rely on the current behavior. Either way, it's good > to discuss this issue before adopting the callback API, so I can make > sure the correct behavior, whatever that turns out to be, is both > documented and tested prior to acceptance.
Thanks for the explanation. :) As long as we're all in agreement that this needs further discussion, then I'll get out of the way... veto rescinded. --Cliff
