5.38 shipped with a minimal implementation, and you can use
Feature::Compat::Class to use it on earlier versions.
Object::Pad is the CPAN testbed, and is more full featured.
On 11/25/24 10:10, [email protected] wrote:
I've heard of moose, and seen some examples, but never used it.
Ive never heard of corinna until Bill's email yesterday,
At which point i read some tutorials and watched at least 1 video,
And i love, love, love the compactness of corinna.
Single inheritance is... eh... fine.
The only thing that gives me pause is that its
experimemtal, and all things perl related seem to
take years to sort out whether they will last or not.
Granted a lot of that is from the years and years of
talk about perl 6. I dont -think- corinna is amother
Perl6 development. I think there are only 4 keywords.
But i read posts from 2 years ago about corinna being
A thing, and its still not a thing. I dont have a good
sense for how much longer it might be to complete.
Greg
On 2024-11-25 08:08, Morse, Richard E.,MGH wrote:
Hi! I don’t think there’s _one_ gold standard yet? I also admit to
not being the most on top of this, but I think that in Perl, your
choices are:
- the new (“Corinna”) object system, if you can require a recent
version of Perl and if the (currently limited) set of abilities suffices
- Moo if you want a fairly light-weight version of Moose — it can’t
quite do everything, but it covers the basic cases, and can easily be
upgraded to Moose
- Moose if you want everything and the kitchen sink
Of course, you can always use the existing OO system. There’s a ton
of modules on CPAN for other object systems. I think that Mojolicious
has a built-in OO system that might be usable? I remember some others
showing up in Advent calendars in the past…
Ricky
On Nov 24, 2024, at 8:02 PM, [email protected] wrote:
External Email - Use Caution
Had an idea for some non-work related perl code that would almost
certainly have to be object oriented/class based.
I'd also like it to maybe be something to make open source for
others to use. So, i would be looking for something that is kinda
"core", considered the "gold standard" for doing oo perl, emphasis
on "standard".
I confess, i have fallen out of touch with whatever is the latest
and greatest for doing OO in perl. Last time I looked, it was moose.
But now Raku is out, and i havent been following it at all. I just
havent had the time to code for fun like i used to. And while i use
a LOT of perl at work, its always glue scripts tying unix commands
together and parsing log files and such. Lots of regexes, zero classes.
I have written a lot of oo perl, but it was all blessed hash refs
stuff, and thats just terrible.
Anyway, if someone could point me to whatever is the latest
greatest, gold standard method for OO perl, i would appreciate it.
And if the answer is "use raku", then i may need a primer on raku,
cause every time ive looked at raku, i get confused and go back to
perl. Or maybe i need to stick with the best standard, but
specifically for perl.
Any pointers would be appreciated
Greg
_______________________________________________
Boston-pm mailing list
[email protected]
https://secure-web.cisco.com/1HKvo1kM36VA2S8K8UKbMmxiENOekzDpLTkj6cG-jB7wENMh407vObRmKccbM2xfzuFkai0n4iQKwASMmu1uq_2bWhtx-mKcuxaePqf03-uypahU8TvT6xLugZX0dKj-KIin2NGz3IHWxNufmuVGH9mZV7X6xSxa7i1GxTf8iX75QaTi6pBP9D-fGxeDWhcJf_puFldxTH9GyurI8beuhe27b7dPBtAaVb7mDuMmT4S9RbB8J2EzZ9PizN4JIuFXRQuczbXrMgVl3iC4StrxB-NDAPYydh7_Bighv-S1CQZnwms7CFfhysmw9i4DPqimG/https%3A%2F%2Fmail.pm.org%2Fmailman%2Flistinfo%2Fboston-pm
The information in this e-mail is intended only for the person to
whom it is addressed. If you believe this e-mail was sent to you in
error and the e-mail contains patient information, please contact the
Mass General Brigham Compliance HelpLine at
https://www.massgeneralbrigham.org/complianceline
<https://www.massgeneralbrigham.org/complianceline> .
Please note that this e-mail is not secure (encrypted). If you do
not wish to continue communication over unencrypted e-mail, please
notify the sender of this message immediately. Continuing to send or
respond to e-mail after receiving this message means you understand
and accept this risk and wish to continue to communicate over
unencrypted e-mail.
_______________________________________________
Boston-pm mailing list
[email protected]
https://mail.pm.org/mailman/listinfo/boston-pm
_______________________________________________
Boston-pm mailing list
[email protected]
https://mail.pm.org/mailman/listinfo/boston-pm
