The reason we ended up at ./method was simply because it was the best 
suggestion anyone had.

Compared to the previous suggestions it was way ahead.

It's other advantage is that (except for on nordic keyboards) dot and 
slash are generally right next to each other, so the expense of using it 
is two chars and one fingering position, as they would likely be hit by 
fourth and fifth fingers (for touch typist style) and some other two 
fingers for the rest of us, and only 1 cm travel for hunt and peck.

It has a very low RSI index :)   (something I don't think we take into 
account enough as it is when we use the Huffman name to justify 
shortening something)

So call it (2ch|2key|1pos|1cm) cost

.::method on the other hand is 2 chars, 4 keystrokes, one of which must 
be held down between the two colons, is a strech for touch typists, 
requires you to get you hand completely away from the letters for the 
rest, and god help the hunt and peckers.

Something like (3ch|4.5key|2pos|5cm) cost.

And I dislike having a THIRD sigil even more than I dislike the second.

Adam K

>  I think $ is way more objectionable to the lily-white non-Perl heathens, but
>  I don't really care about them either way.  I'm just saying ./ screams "file
>  path" to me, or maybe even "typo-ed Java/C++ comment" or something.
>  Certainly not "method invocation" or "implicit invocant."  The .: thing,
>  OTOH, totally works for me and I've always liked it.  I'm just trying to
>  stretch it to cover both public and private.  Maybe there's something better
>  than both.