Re: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see?

Replies are listed 'Best First'.
Re^2: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Your Mother (Archbishop) on Oct 27, 2019 at 02:37 UTC
Weighing in here ... why not ... You omitted the question mark so that the rhetorical nature of the “question” was understood I suppose. Unfortunately, too many of us understand the answer to the literal question. :\| It’s terribly ironic—one wonders if it wasn’t subconscious self-sabotage, if that isn’t the underlying motive to everything, if there isn’t some sort of satisfaction derived from the public humiliation—that you would suggest moving the steering wheel to the other side of the car…	[reply]
Re^2: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Anonymous Monk on Oct 26, 2019 at 21:19 UTC
My last post on PerlMonks ... ???	[reply]
Re^2: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Anonymous Monk on Oct 27, 2019 at 02:20 UTC
Designers seem to conveniently forget that there are many millions of lines of production source-code in production service that will be immediately impacted – rendered useless – by even the slightest design decision that they might make ... unless they have both prepared and promoted as a new standard a way by which both legacy and new software can co-exist. Which they never do. Deprecation is vandalism! I've been saying it for years. I guess they keep doing it because it costs money to fix code and the more you break the more you make!	[reply]
Re^3: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Your Mother (Archbishop) on Oct 27, 2019 at 07:23 UTC
Pessimistic, ignorant, and paranoid. Weird—but entirely banal—flex.	[reply]
Re^4: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Anonymous Monk on Oct 31, 2019 at 10:09 UTC
In my ever growing MyPAN dependencies don't break because you don't ever have to deprecate. _🕷 The impulse to subtract from software may be an opportunity to expand it in disguise. _🐜 Certain types of bugs can be developed into features rather than trying to eliminate them. _🐛 A recent example on this site was a module that broke another module by deprecating the two-arg form of a method in favor of a new two-arg method, and instead of detecting two-args in the old method and aliasing that to the new method, the use of two-args in the old method was first deprecated then made fatal. I would never do that because it seems malicious and destructive and aggressive like... code rage! 🎻 Yet some respectable authors of some excellent tools that some of us mere mortals come to depend on do this all the time. They always have a reasonable excuse why I have to add one more character to 5000 lines of code because all of a sudden "Unescaped left brace in regex is illegal"! 2¢ from a humble perl hacker who does not deprecate 💩 and wishes others would be as considerate of their own software. 🌈 🦄 `perl -ML -e'print Software::License::Perl_5->new({holder=>join" ",@ARG +V})->notice' Just another Perl hacker` [download]	[reply] [d/l]
Re^5: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Your Mother (Archbishop) on Oct 31, 2019 at 16:17 UTC
Re^6: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by Anonymous Monk on Oct 31, 2019 at 18:39 UTC
Re^5: If Perl 5 were to become Perl 7, what (backward-compatible) features would you want to see? by soonix (Canon) on Oct 31, 2019 at 12:38 UTC


go ahead... be a heretic
	PerlMonks