From: Yehuda Katz <wycats@...>
Date: 2009-02-20T07:49:11+09:00
Subject: [ruby-core:22273] Re: YASNP (Yet Another Selector Namespace 	Proposal)

--000e0cd228b8abe23504634d5864
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I'd be perfectly happy to have it take a block.

-- Yehuda

2009/2/19 Charles Oliver Nutter <charles.nutter@sun.com>

> Yehuda Katz wrote:
>
>> I would be open to making it take a block, but I'm not aware of any
>> use-case where that would be helpful, so I left it out at the beginning to
>> reduce the need for extra ceremony.
>>
> ...
>
>> Again, I'm open to doing it a different way. I chose this initially
>> because it makes it easier to implement at parse-time (which is required for
>> performance) and because I can't think of any use-case where more granular
>> application of namespaces would actually be useful, but I'd be fine with
>> "use" taking a block if it moved the proposal forward.
>>
>
> I suppose there's another argument in favor of an explicit bounding of the
> "use" area: where do you *start*? If this is parse time, having it start at
> the first "use" call seems a little odd; you'd almost want it to be a
> whole-file pragma. But starting it at the beginning of the file seems just
> as odd, since a use anywhere in the body changes all method dispatches.
>
> - Charlie
>
>


-- 
Yehuda Katz
Developer | Engine Yard
(ph) 718.877.1325

--000e0cd228b8abe23504634d5864
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I&#39;d be perfectly happy to have it take a block.<br><br>-- Yehuda<br><br=
><div class=3D"gmail_quote">2009/2/19 Charles Oliver Nutter <span dir=3D"lt=
r">&lt;<a href=3D"mailto:charles.nutter@sun.com">charles.nutter@sun.com</a>=
&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class=3D"Ih2=
E3d">Yehuda Katz wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would be open to making it take a block, but I&#39;m not aware of any use=
-case where that would be helpful, so I left it out at the beginning to red=
uce the need for extra ceremony.<br>
</blockquote></div>
...<div class=3D"Ih2E3d"><br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Again, I&#39;m open to doing it a different way. I chose this initially bec=
ause it makes it easier to implement at parse-time (which is required for p=
erformance) and because I can&#39;t think of any use-case where more granul=
ar application of namespaces would actually be useful, but I&#39;d be fine =
with &quot;use&quot; taking a block if it moved the proposal forward.<br>

</blockquote>
<br></div>
I suppose there&#39;s another argument in favor of an explicit bounding of =
the &quot;use&quot; area: where do you *start*? If this is parse time, havi=
ng it start at the first &quot;use&quot; call seems a little odd; you&#39;d=
 almost want it to be a whole-file pragma. But starting it at the beginning=
 of the file seems just as odd, since a use anywhere in the body changes al=
l method dispatches.<br>

<br>
- Charlie<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Yehuda Katz<br>Develope=
r | Engine Yard<br>(ph) 718.877.1325<br>

--000e0cd228b8abe23504634d5864--