From: Yehuda Katz <wycats@...>
Date: 2009-02-25T17:26:30+09:00
Subject: [ruby-core:22459] Re: YASNP (Yet Another Selector Namespace 	Proposal)

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

To be honest, I'm not sure what Rubinius' experience has anything to do with
the desire for namespacing. I could see why it would be useful for *users*
of Rubinius, but as there aren't any users, yet, the issues that would
likely cause them to want some kind of selector namespaces would not have
come up yet. On the other hand, conflicts between Rails and Merb (or more
realistically, Merb and ActiveRecord) have already happened in the wild, and
have clearly illustrated the real-life need for something like this.

I'm really interested in a *real* example of the fears people have about
this feature. So far all I've seen is vague fearmongering...

-- Yehuda

2009/2/25 Yukihiro Matsumoto <matz@ruby-lang.org>

> Hi,
>
> In message "Re: [ruby-core:22427] Re: YASNP (Yet Another Selector Namespace
> Proposal)"
>     on Wed, 25 Feb 2009 07:04:34 +0900, Brian Ford <brixen@gmail.com>
> writes:
>
> |In implementing Rubinius, we have only encountered one major issue
> |with redefining a core library method: mathn changing Fixnum#/.
>
> Interesting.  I thought people behind Rubinius would love (or even
> demand) some kind of selector namespace, to protect their core
> libraries from users' monkey patching.
>
>                                                        matz.
>
>


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

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

To be honest, I&#39;m not sure what Rubinius&#39; experience has anything t=
o do with the desire for namespacing. I could see why it would be useful fo=
r *users* of Rubinius, but as there aren&#39;t any users, yet, the issues t=
hat would likely cause them to want some kind of selector namespaces would =
not have come up yet. On the other hand, conflicts between Rails and Merb (=
or more realistically, Merb and ActiveRecord) have already happened in the =
wild, and have clearly illustrated the real-life need for something like th=
is.<br>
<br>I&#39;m really interested in a *real* example of the fears people have =
about this feature. So far all I&#39;ve seen is vague fearmongering...<br><=
br>-- Yehuda<br><br><div class=3D"gmail_quote">2009/2/25 Yukihiro Matsumoto=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:matz@ruby-lang.org">matz@ruby-lang=
.org</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;">Hi,<br>
<br>
In message &quot;Re: [ruby-core:22427] Re: YASNP (Yet Another Selector Name=
space Proposal)&quot;<br>
<div class=3D"Ih2E3d"> =A0 =A0on Wed, 25 Feb 2009 07:04:34 +0900, Brian For=
d &lt;<a href=3D"mailto:brixen@gmail.com">brixen@gmail.com</a>&gt; writes:<=
br>
<br>
|In implementing Rubinius, we have only encountered one major issue<br>
|with redefining a core library method: mathn changing Fixnum#/.<br>
<br>
</div>Interesting. =A0I thought people behind Rubinius would love (or even<=
br>
demand) some kind of selector namespace, to protect their core<br>
libraries from users&#39; monkey patching.<br>
<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0matz.<br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Yehuda Katz<br>Develope=
r | Engine Yard<br>(ph) 718.877.1325<br>

--000e0cd23ef0e2208f0463ba00fa--