VisualWorks' interpretation if anyone cares,

#yourself numArgs = 0.
#'**' numArgs = 1.
#at: numArgs = 1.
#at:put: numArgs = 2.
#'a:b:c' numArgs = 2.
#'a::bc' numArgs = 2.
#':abc:' numArgs = 3.
#'::abc' numArgs = 3.
#':abc' numArgs = 2.
#':::' numArgs = 4.

Not a whole lot better, but at least no negatives in the list ;)

Cheers!

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org
[mailto:squeak-dev-
> bounces at lists.squeakfoundation.org] On Behalf Of Bert Freudenberg
> Sent: Friday, July 27, 2007 4:54 PM
> To: The general-purpose Squeak developers list
> Subject: Re: What is the meaning of numArgs
> 
> 
> On Jul 28, 2007, at 1:48 , nicolas cellier wrote:
> 
> > "i can understand valid selectors:"
> >
> > "Unary:"
> > #yourself numArgs = 0.
> >
> > "Binary:"
> > #'**' numArgs = 1.
> >
> > "Keywords"
> > #at: numArgs = 1.
> > #at:put: numArgs = 2.
> >
> >
> > "But does anyone knows what the following cases are meaning?"
> > #'a:b:c' numArgs = 1.
> > #'a::bc' numArgs = 1.
> > #':abc:' numArgs = 0.
> > #'::abc' numArgs = -1.
> > #':abc' numArgs = -2.
> >
> >
> > #':::' numArgs. "make your guess here"
> >
> 
> I guess these are remnants of the experiments with alternate
> syntaxes, which allowed leading and trailing parts of identifiers
> IIRC (e.g., "if ... then ... end" would be a valid expression and the
> selector ":if:then:end" - I'm making this up, but something along the
> lines was supported).
> 
> - Bert -
> 
>