Skip to Content.
Sympa Menu

devel - Re: [sympa-developpers] sympatic: OO or not OO ?

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: IKEDA Soji <address@concealed>
  • To: Marc Chantreux <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-developpers] sympatic: OO or not OO ?
  • Date: Fri, 16 Mar 2018 16:15:07 +0900

On Fri, 16 Mar 2018 07:33:01 +0100
Marc Chantreux <address@concealed> wrote:

> hello Soji,
>
> On Fri, Mar 16, 2018 at 08:19:15AM +0900, Soji Ikeda wrote:
> > I think wrapper module Sympatic is not required (I don’t know why this
> > option is ignored).
>
> Nothing is required: this is all about convenience.
>
> > If Moo is required, use Moo in the source. If it is not, don’t use it.
> > What we need is to decide whether we use it or not.
>
> please note there is no long debate on it: racke made a proposal and
> it was picked because this part is really about just lazyness.

Because Moo was not controversial. No matter short debate itself.

> > We need not tasking our brain to decide whether we prepare cryptic
> > import option for it or not.
>
> * having a general policy for all the codebase without worring
> about the author of one particular module to use it or not
> is *good*.
> * every long topic we rised by sympatic where something that must be
> debated anyway. sympatic just push them all in once.

On former:

If someone worried, they may read existing code. Moreover, if
someone want to propose other or additional module, they may
propose, and if necessary, they may submit code using such module
and we may examine it.

Authors don't want to know feature of wrapper module, but want to
write code.

On latter:

It is not the reason why we should use homemade wrapper module in
actual code.

> > For example, if I propose to include
> > MooX::Singleton, what will we do?
>
> you do realize that Singleton is a special (rare) case, right ?
> so it means there is nothing to do with sympa.
>
> if you need a Singleton:
>
> * go public about adding the MooX::Singleton as sympa dependency
> * if accepted, add MooX::Singleton (if not, deal with your
> conscience: you're the sympa6.2 branch man anyway)
>
> * if accepted
> * add MooX::Singleton on the sympa dependency
> * use MooX::Singleton that way
>
> use Sympatic;
> use MooX::Singleton;
>
> > Instead of thinking about what is to be included in Sympatic, let’s
> > think about how we will use.
>
> i just don't understand because that's exactly what we did when we
> talked about autodie: talking about how to use it and finally get a grid
> of it.

I'm understanding we did what we had to do: talking about how to use
it and finally getting rid of it.

(BTW You have said you will show the usage of your proposal applying
to practical code of Sympa. If anything, you have not done it.)

After all, our discussion has been focusing on usability of each
module (even if not chosen as content of Sympatic).


In short, I think wrapper module Sympatic is not required.


Regards,
-- Soji


> marc


--
株式会社 コンバージョン
ITソリューション部 システムソリューション1グループ 池田荘児
〒140-0014 東京都品川区大井1-49-15 アクセス大井町ビル4F
e-mail address@concealed TEL 03-6429-2880
https://www.conversion.co.jp/



Archive powered by MHonArc 2.6.19+.

Top of Page