From: "Mário Luan" Date: 2012-12-07T03:36:53+09:00 Subject: Re: Organizing code to avoid name space collision --047d7b343b04e42fc304d03361a6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable @Sergey , You may mark *ruby-talk@ruby-lang.org* as spam on your email service. Cheers! *M=C3=A1rio Luan* *Linkedin* *facebook.com/mariosouzaluan * *@mario_luan * *TIM (11) 59506744* *OI (11) 98033-5954* 2012/12/6 Sergey Zhikharev > Hello, friend > > Excuse me please, how can I unsubscribe from it? > > -- > With best regards, > S.Z > > > -----Original Message----- > From: Robert Klemme [mailto:shortcutter@googlemail.com] > Sent: Thursday, December 06, 2012 2:29 PM > To: ruby-talk ML > Subject: Re: Organizing code to avoid name space collision > > On Thu, Dec 6, 2012 at 11:52 AM, Martin Hansen > wrote: > >> How is it decided which of the two is included in regular code? > > > > I decide if I want backtrack or dynamic matching in the scripts I write > > - and include accordingly. > > > >>> I also explored your extend solution, but while that should work (I > didn't > >>> test) it means that every time I instantiate a Seq object I need to > >>> extend it. I could accept that for the testing files, but I think it > >>> would obfuscate the regular code that uses Seq objects. > >> > >> Not at all. You can do it in #initialize. No caller would need to > >> change. > > > > OK, extend is the solution. Many thanks Robert. > > You're welcome! > > Kind regards > > robert > > -- > remember.guy do |as, often| as.you_can - without end > http://blog.rubybestpractices.com/ > > > --047d7b343b04e42fc304d03361a6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable @Sergey=C2=A0,

You may mark ruby-talk@ruby-lang.org as spam on your email= service.

Cheers!<= /span>


M=C3=A1rio Luan
Linkedin
TIM (1= 1) 59506744
OI (11) 98033-5954



2012/12/6 Sergey Zhikharev <s.= zhikharev@systemtele.com>
Hello, friend

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Excuse me please, how can I unsubscribe from it= ?

--
With best regards,
S.Z

-----Original Message-----
From: Robert Klemme [mailto:s= hortcutter@googlemail.com]
Sent: Thursday, December 06, 2012 2:29 PM
To: ruby-talk ML
Subject: Re: Organizing code to avoid name space collision

On Thu, Dec 6, 2012 at 11:52 AM, Martin Hansen <lists@ruby-forum.com> wrote:
>> How is it decided which of the two is included in regular code? >
> I decide if I want backtrack or dynamic matching in the scripts I writ= e
> - and include accordingly.
>
>>> I also explored your extend solution, but while that should wo= rk (I
didn't
>>> test) it means that every time I instantiate a Seq object I ne= ed to
>>> extend it. I could accept that for the testing files, but I th= ink it
>>> would obfuscate the regular code that uses Seq objects.
>>
>> Not at all. =C2=A0You can do it in #initialize. =C2=A0No caller wo= uld need to
>> change.
>
> OK, extend is the solution. Many thanks Robert.

You're welcome!

Kind regards

robert

--
remember.guy do |as, often| as.you_can - without end
http://blo= g.rubybestpractices.com/



--047d7b343b04e42fc304d03361a6--