Re^6: Perl archeology: Need help in refactoring of old Perl code that does not use strict (hurry up and wait)

You don't consider Larry's copying of Python's object model for Perl 5 as a significant Python influence on Perl OO?

Another such quote was mentioned here before: Re^6: Something to meditate on -- the need for a trendy perl?

Comment on Re^6: Perl archeology: Need help in refactoring of old Perl code that does not use strict (hurry up and wait)

Replies are listed 'Best First'.
Re^7: Perl archeology: Need help in refactoring of old Perl code that does not use strict (hurry up and wait) by eyepopslikeamosquito (Archbishop) on Nov 15, 2017 at 21:12 UTC
Yes, you're right, Python was a significant influence on the early Perl 5 object system in the 1990s. And passing 'self' as the first parameter to access object state still endures today. My original gut reaction to the claim that Moose is "Perl trying to keep up with Python in the OO domain" still stands; that is, Python's OO system hasn't been the inspiration for enhancing Perl's OO capabilities since around the year 2000 or so. Thanks for the link. Though (for some definition of object) everything is an object in Python, it's not a pure OO language, rather it's a pragmatic multi-paradigm language. Like Perl. IMHO, Perl and Python remain similar pragmatic, multi-paradigm languages, the main point of (philosophical) difference being Perl's TMTOWTDI ("There's more than one way to do it"), or the more recent TimToadyBicarbonate ("There's more than one way to do it, but sometimes consistency is not a bad thing either"), versus Python's TOOWTDI ("There should be one -- and preferably only one -- obvious way to do it").	[reply]

Replies are listed 'Best First'.

Re^7: Perl archeology: Need help in refactoring of old Perl code that does not use strict (hurry up and wait)
by eyepopslikeamosquito (Archbishop) on Nov 15, 2017 at 21:12 UTC

Yes, you're right, Python was a significant influence on the early Perl 5 object system in the 1990s. And passing 'self' as the first parameter to access object state still endures today.

My original gut reaction to the claim that Moose is "Perl trying to keep up with Python in the OO domain" still stands; that is, Python's OO system hasn't been the inspiration for enhancing Perl's OO capabilities since around the year 2000 or so.

Thanks for the link. Though (for some definition of object) everything is an object in Python, it's not a pure OO language, rather it's a pragmatic multi-paradigm language. Like Perl.

IMHO, Perl and Python remain similar pragmatic, multi-paradigm languages, the main point of (philosophical) difference being Perl's TMTOWTDI ("There's more than one way to do it"), or the more recent TimToadyBicarbonate ("There's more than one way to do it, but sometimes consistency is not a bad thing either"), versus Python's TOOWTDI ("There should be one -- and preferably only one -- obvious way to do it").

[reply]