Re^7: Modernizing the Postmodern Language?


XP is just a number
	PerlMonks

Re^7: Modernizing the Postmodern Language?

by hippo (Bishop)

on Jul 16, 2020 at 08:38 UTC ( [id://11119395]=note: print w/replies, xml )

Need Help??

in reply to Re^6: Modernizing the Postmodern Language?
in thread Modernizing the Postmodern Language?

it's always felt backwards to me that the burden is on users of new releases to enable new, non-experimental things to prevent users who don't update their Perl from having to update their code.

Philosophically I would agree. The move to v7 isn't a philosophical one, however; it's a practical one. From a practical standpoint I really can't see how having one line of boilerplate of maybe 10 characters or so can really be classed as a burden. To follow your path I would only need to add it once to my stock script/module template and we're done. And given that this replaces the current, longer boilerplate it's even better. Your new code is shorter, slicker and has all the new features and those still having to support 5.6.0 need do nothing. In the immortal words of the late, great Errol Brown, "Everyone's a winner, baby!".

Comment on Re^7: Modernizing the Postmodern Language?

Replies are listed 'Best First'.

Re^8: Modernizing the Postmodern Language?
by salva (Canon) on Jul 16, 2020 at 09:17 UTC

I really can't see how having one line of boilerplate of maybe 10 characters or so can really be classed as a burden.

Besides that, the day Perl 8 comes out, you will be facing the same issue again. You may require people to add a use v8 pragma, or otherwise, require people to change their old Perl 7 code inserting the use v7 one.

So, in any case, you will have to add the use v7 pragma, the only question is when!

[reply]
[d/l]
[select]

In Section Meditations