On 02/22/2011 04:37 PM, Amit Shah wrote:
On (Tue) 22 Feb 2011 [15:28:59], Avi Kivity wrote:
> On 02/22/2011 01:17 PM, Amit Shah wrote:
> >On (Tue) 22 Feb 2011 [13:09:34], Avi Kivity wrote:
> >> On 02/22/2011 12:18 PM, Amit Shah wrote:
> >> >Mark the current iohandler list as 'old'. In the next commit we'll
> >> >introduce a new iohandler api that will replace the list name.
> >> >
> >> >The 'old' list will eventually be completely replaced by the new
> >> >implementation.
> >>
> >> A better way to do this is to implement the old API in terms of the
> >> new API. This ensures you don't lose any functionality, and reduces
> >> the amount of low-level infrastructure.
> >
> >With this new approach of switching to just one callback, that is more
> >work for little gain as we'll just deprecate the older API soon. (The
> >previous patches used this approach, btw.)
>
> Does "deprecate" mean "completely remove"?
>
> If so I agree.
Yes, completely removing the older API is the plan (as noted in
message 00).
Great. That's a much better deprecate than "add the new thing and let
the old thing rot" (which I've been guilty of a few times).
--
error compiling committee.c: too many arguments to function
