Front page | perl.perl5.porters |
Postings from July 2022
Re: 'class' feature has begun / initial tidying PRs
Thread Previous
|
Thread Next
From:
oodler577
Date:
July 5, 2022 14:02
Subject:
Re: 'class' feature has begun / initial tidying PRs
Message ID:
Pine.NEB.4.64.2207051306300.11573@odin.sdfeu.org
On Fri, 1 Jul 2022, Matthew Persico wroten
> Date: Fri, 1 Jul 2022 13:11:37 -0400
> From: Matthew Persico <matthew.persico@gmail.com>
> To: Ovid <curtis.poe@gmail.com>
> Cc: Paul LeoNerd Evans <leonerd@leonerd.org.uk>,
> Perl5 Porters <perl5-porters@perl.org>
> Subject: Re: 'class' feature has begun / initial tidying PRs
>
> This is great news. Here's my USD 0.02:
>
> The most important piece of information to remember and disseminate about
> this work is that we are NOT CHANGING ANYTHING ABOUT THE EXISTING OO
> METAPHOR OR OO IMPLEMENTATION in Perl. bless() is not going away, nor are
> any of the modules based on bless(). This is an ADDITION, a side-by-side,
> TMTOWTDI enhancement to Perl that we hope will lead to easier OO usage down
> the road, including for those coming to Perl from other languages. No one
> is suggesting that a mass-rewrite (a la Python) of any existing OO code
> will be required.
>
> Of course, I am preaching to the choir here, but I believe it's
> very important to tell anyone who says otherwise, or just asks, that
> Corrina is "only" an ADDITION to Perl.
This is a good point. I have never had the impression that any of this was
getting replaced or changed in anyway; but that doesn't mean I have not
been concerned about how this is happening or what "Perl" in the wild will
end up looking like as a result. So on one hand what you say is true; on
the other it grade A copium. I already am worthless on codebases that use
Moose, so for me this is just another way to disqualify the code I work
with.
I curious about what this looks like mixed in with "traditional" Perl.
I guess I am just a simple person, wanting really a "bless" that made it
easy to do define accessors. I finally got this when Util::H2O cam on the
scene; the next step was a simple wrapper around it to get Util::H2O::More's
C<baptise>.
To Moose's credit, it did usher in a spike in cool new Perl modules and
code; if it did nothing else, it unlocked the potential for a lot of
developers. I expect the same with this approach to Perl OOP. Only time
will tell how effective this will be in making existin Perl programmers
more productive and attacting new programmers to the language.
Cheers,
Brett
>
> EOSOAPBOX
>
> On Fri, Jul 1, 2022 at 9:45 AM Ovid <curtis.poe@gmail.com> wrote:
>
>> On Fri, Jul 1, 2022 at 1:01 PM Paul "LeoNerd" Evans <
>> leonerd@leonerd.org.uk> wrote:
>>
>>> Help, howso?
>>>
>>> * You can still checkout / build / install from that branch and run it
>>> locally to try things out.
>>>
>>> * Alternatively, if you want to write new test cases to live in the
>>> t/class/ directory, you can still do that too and send
>>> patches/files/etc... in some way.
>>>
>>> Do either of those ideas answer your question?
>>>
>>
>>
>> Yes, they do. Thank you!
>>
>> Curtis "Ovid" Poe
>> CTO, All Around the World
>> World-class software development and consulting
>> https://allaroundtheworld.fr/
>>
>
>
> --
> Matthew O. Persico
>
oodler577@sdfeu.org
SDF-EU Public Access UNIX System - http://sdfeu.org
Thread Previous
|
Thread Next