Maciej Stachowiak:
> > I think [NativeObject] should be renamed to [Callback]. It is meant to
> > be used for callback objects that have a single designated callback
> > method, right?
Cameron McCormack:
> Not only a single callback method, perhaps multiple. But yes, it’s
> pretty much for cal
Hi Maciej and Anne.
Maciej Stachowiak:
> I think [NativeObject] should be renamed to [Callback]. It is meant to
> be used for callback objects that have a single designated callback
> method, right?
Not only a single callback method, perhaps multiple. But yes, it’s
pretty much for callbacks.
On Oct 3, 2008, at 2:58 AM, Anne van Kesteren wrote:
On Fri, 03 Oct 2008 05:40:26 +0200, Maciej Stachowiak
<[EMAIL PROTECTED]> wrote:
I think [Variadic] should be renamed [Optional]. A function may be
variadic, but a parameter is optional, and this goes on the
parameter.
To me [Option
On Fri, 03 Oct 2008 05:40:26 +0200, Maciej Stachowiak <[EMAIL PROTECTED]>
wrote:
I think [Variadic] should be renamed [Optional]. A function may be
variadic, but a parameter is optional, and this goes on the parameter.
To me [Optional] does not really convey zero or more arguments very well
I think [NativeObject] should be renamed to [Callback]. It is meant to
be used for callback objects that have a single designated callback
method, right?
I think [Variadic] should be renamed [Optional]. A function may be
variadic, but a parameter is optional, and this goes on the paramet
