From: Eric Mahurin <eric.mahurin@...>
Date: 2008-04-24T23:00:59+09:00
Subject: Re: [RCR] Drop :: as a . synonym

------=_Part_32_16157240.1209045657607
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 4/24/08, Michael Neumann <mneumann@ntecs.de> wrote:
>
> Eric Mahurin wrote:
> > I'd actually prefer to go the other way and  add  more value to both
> > "::" and ".".
> >
> > a::b - gives an object named b in the scope of a
> > a.b - calls an object named b in the scope of a
>
> Nice idea, but a::b::c doesn't make any sense, right? Or is it method
> "c" of the Proc object method(:b)?


Yep.  So, a::b::arity would probably be a better example.  A chain of these
"::" would typically have uppercase constants that could be arbitrary
objects (typically class/module) for all except the last that would refer to
a method.  The first in a chain might also be lowercase (or an expression)
if it is a class/module.

A possibly even better idea would be to have "::" as an overloadable
operator.  Then you could make objects that look like classes or modules
with a scope of "constants".  You could also make "." follow this
overloading (call the object from the "::" operator).

I know some of you might be seeing the similarity to python.  You can do
similar things with its overloadable "." operator (attribute accessor) and
overloable "()" operator (call).  The above would give you something similar
in a ruby syntax.  I still think it would be nice to have an overloadable
call operator like python, so you don't have to #call a Proc/Method.  Or
allow #[] to take a block like a normal method call (#[] would be just as
good then).

------=_Part_32_16157240.1209045657607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 4/24/08, <b class="gmail_sendername">Michael Neumann</b> &lt;<a href="mailto:mneumann@ntecs.de">mneumann@ntecs.de</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Eric Mahurin wrote:<span class="q"><br></span>&gt; I&#39;d actually prefer to go the other way and &nbsp;add &nbsp;more value to both<br>
&gt; &quot;::&quot; and &quot;.&quot;.<br>
&gt;<br>
&gt; a::b - gives an object named b in the scope of a<br>
&gt; a.b - calls an object named b in the scope of a<br>
<br>
Nice idea, but a::b::c doesn&#39;t make any sense, right? Or is it method<br>
&quot;c&quot; of the Proc object method(:b)?</blockquote><div><br>Yep.&nbsp; So, a::b::arity would probably be a better example.&nbsp; A chain of these &quot;::&quot; would typically have uppercase constants that could be arbitrary objects (typically class/module) for all except the last that would refer to a method.&nbsp; The first in a chain might also be lowercase (or an expression) if it is a class/module.<br>
<br>A possibly even better idea would be to have &quot;::&quot; as an overloadable operator.&nbsp; Then you could make objects that look like classes or modules with a scope of &quot;constants&quot;.&nbsp; You could also make &quot;.&quot; follow this overloading (call the object from the &quot;::&quot; operator).<br>
<br>I know some of you might be seeing the similarity to python.&nbsp; You can do similar things with its overloadable &quot;.&quot; operator (attribute accessor) and overloable &quot;()&quot; operator (call).&nbsp; The above would give you something similar in a ruby syntax.&nbsp; I still think it would be nice to have an overloadable call operator like python, so you don&#39;t have to #call a Proc/Method.&nbsp; Or allow #[] to take a block like a normal method call (#[] would be just as good then).<br>
<br></div></div>

------=_Part_32_16157240.1209045657607--