From: Yehuda Katz Date: 2009-02-24T01:08:29+09:00 Subject: [ruby-core:22372] Re: YASNP (Yet Another Selector Namespace Proposal) --000e0cd1a676d5c0c004639838f1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Can you explain *why* you don't like it? Keep in mind that most people would never use this feature... it's mostly for frameworks to be able to make core extensions for their own use without polluting the global space. -- Yehuda 2009/2/23 Berger, Daniel > > > > -----Original Message----- > > From: Eero Saynatkari [mailto:ruby-ml@kittensoft.org] > > Sent: Sunday, February 22, 2009 7:56 AM > > To: ruby-core@ruby-lang.org > > Subject: [ruby-core:22330] Re: YASNP (Yet Another Selector > > Namespace Proposal) > > > > Excerpts from Aaron Patterson's message of Sun Feb 22 > > 04:35:41 +0200 2009: > > > On Sun, Feb 22, 2009 at 04:34:18AM +0900, Jim Weirich wrote: > > > > On Feb 20, 2009, at 8:39 AM, Yehuda Katz wrote: > > > >> - no special namespace keyword; any module can be a namespace > > > > > > > > +1 > > > > > > > > I like this much better than giving the use command its own block. > > > > > > +1 as well, but I like the block. For me, it seems to be > > more clear > > > +as > > > to what is going on. > > > > > > use Merb::String => String do > > > "bla blah".some_special_merb_only_method > > > end > > > > > > I am not sure I like this plan at all, really: it would be > > better to implement through (or at least concurrently with) > > methodwise selectors, but since this version is not dealing > > with an actual block, it should follow the while/until > > pattern instead: > > > > using Merb::String => String > > whatever > > end > > Put me in the "don't like" category as well. > > Regards, > > Dan > -- Yehuda Katz Developer | Engine Yard (ph) 718.877.1325 --000e0cd1a676d5c0c004639838f1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Can you explain *why* you don't like it?

Keep in mind that most = people would never use this feature... it's mostly for frameworks to be= able to make core extensions for their own use without polluting the globa= l space.

-- Yehuda

2009/2/23 Berger, Daniel <Daniel.Berge= r@qwest.com>

> -----Original Message-----
> From: Eero Saynatkari [mailto:ruby-ml@kittensoft.org]
> Sent: Sunday, February 22, 2009 7:56 AM
> To: ruby-core@ruby-lang.org=
> Subject: [ruby-core:22330] Re: YASNP (Yet Another Selector
> Namespace Proposal)
>
> Excerpts from Aaron Patterson's message of Sun Feb 22
> 04:35:41 +0200 2009:
> > On Sun, Feb 22, 2009 at 04:34:18AM +0900, Jim Weirich wrote:
> > > On Feb 20, 2009, at 8:39 AM, Yehuda Katz wrote:
> > >> - no special namespace keyword; any module can be= a namespace
> > >
> > > +1
> > >
> > > I like this much better than giving the use command its own = block.
> >
> > +1 as well, but I like the block. For me, it seems to be > more clear
> > +as
> > to what is going on.
> >
> > use Merb::String =3D> String do
> > "bla blah".some_special_merb_only_method<= br> > > end
>
>
> I am not sure I like this plan at all, really: it would be
> better to implement through (or at least concurrently with)
> methodwise selectors, but since this version is not dealing
> with an actual block, it should follow the while/until
> pattern instead:
>
> using Merb::String =3D> String
> whatever
> end

Put me in the "don't like" category as well.

Regards,

Dan

--
Yehuda Katz
Develope= r | Engine Yard
(ph) 718.877.1325
--000e0cd1a676d5c0c004639838f1--