From: Yehuda Katz Date: 2009-02-24T03:13:45+09:00 Subject: [ruby-core:22379] Re: YASNP (Yet Another Selector Namespace Proposal) --000e0cd22d5200626a046399f866 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I'd be fine with "foo".Merb:to_url as one way of accessing the namespace, but frankly, in most cases this is for libraries and frameworks to be able to scope the extent of their changes to Ruby's core. In that context, being able to say: "use this namespace for all of the following code" is quite useful. -- Yehuda 2009/2/23 Eero Saynatkari > Excerpts from Yehuda Katz's message of Mon Feb 23 18:08:29 +0200 2009: > > Can you explain *why* you don't like it? > > It is difficult to see the extent of changes. I prefer the method-wise > namespace: > > "foo".Merb:to_url > > > -- > Magic is insufficiently advanced technology. > > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --000e0cd22d5200626a046399f866 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'd be fine with "foo".Merb:to_url as one way of accessing th= e namespace, but frankly, in most cases this is for libraries and framework= s to be able to scope the extent of their changes to Ruby's core. In th= at context, being able to say: "use this namespace for all of the foll= owing code" is quite useful.

-- Yehuda

2009/2/23 Eero Saynatkari <= span dir=3D"ltr"><ruby-ml@kitt= ensoft.org>

Excerpts from Yehuda Katz's message of Mon Feb 23 18:08:29 +0200 2009:<= br>
> Can you explain *why* you don't like it?

It is difficult to see the extent of changes. I prefer the method-wis= e
namespace:

"foo".Merb:to_url

--
Magic is insufficiently advanced technology.

--
Yehuda Katz=
Developer | Engine Yard
(ph) 718.877.1325
--000e0cd22d5200626a046399f866--