Sara Golemon wrote:
I say mixed to avoid confusing the user with protos like:
somefunc(callback callback);
Of course, if all uses of 'callback' as a parameter name were changed to
something else (and no not 'function') then I'd be okay with the use of
'callback' as a type. 'userfunc' or 'handler'
On Fri, 20 Jun 2003, Philip Olson wrote:
> On Thu, 19 Jun 2003, Sara Golemon wrote:
>
> > > Once that was done, I said that this should be referenced wherever
> > > callbacks are used, to keep it all uniform and neat, rather than each
> > > function that uses callbacks either having a copy and pa
On Thu, 19 Jun 2003, Sara Golemon wrote:
> > Once that was done, I said that this should be referenced wherever
> > callbacks are used, to keep it all uniform and neat, rather than each
> > function that uses callbacks either having a copy and paste or a
> > completely new piece of text on callbac
> Once that was done, I said that this should be referenced wherever
> callbacks are used, to keep it all uniform and neat, rather than each
> function that uses callbacks either having a copy and paste or a
> completely new piece of text on callbacks.
>
Absolutely, language.types.callback (as oppo
