http://qs1969.pair.com?node_id=11139554


in reply to Re^4: sort AoH buggy? (deprecation candidate)
in thread sort AoH buggy?

It's causing more damage than benefit

IYHO, of course. Personally speaking I see it as neither a huge boon nor a terrible disaster.

and fixing old code is easy

It really isn't. Technical debt is a huge problem within the industry - just ask any COBOL programmer (if they will let you onto their superyacht). I have seen comments like

# This next line is essential for this subroutine to work but I don't 
+know why.
# DO NOT TOUCH OR REMOVE IT!

[download]

too many times to be shocked or surprised. Any time you touch old code you risk breakage and the older the code the higher the risk.

The more logical Perl is constructed, the easier it is to promote.

Completely agree (so long as it doesn't end up just being a dialect of python ;-p)

🦛

Replies are listed 'Best First'.
Re^6: sort AoH buggy? (deprecation candidate)
by LanX (Saint) on Dec 10, 2021 at 19:05 UTC
    NB: I said deprecation candidate

    I doubt it's complicated to transform

    • sort my_comp LIST
    to
    • sort {my_comp} LIST
    but YMMV.

    In the end this would boil down to using pragmas to keep old code afloat. And consequently to a similar discussion like use v7; was.

    Problem is that the community has no agreement about the goals and their target groups.

    I'd say they can't even communicate about that, at least in a productive way.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery

[reply]
[d/l]
[select]
      I doubt it's complicated to transform ...

      Not at all in one line of a 20-line script. But to do it reliably across many files in a 1,000,000 line codebase without breaking anything? That's a different matter entirely. Never mind the shops who are running 15-year-old Perl systems with no Perl maintainer on the books.

      a similar discussion like use v7; was.

      Quite so. I applaud the enthusiasm of those who proposed it but to do so in a language which has always striven for backwards compatibility was inevitably going to be a big task. For every agile developer crying, "Throw it all out!" there is a sysadm or project manager with a legacy burden screaming "Keep it all in!".

      🦛

[reply]
[d/l]
        I think it's more complicated and the real problem is communication.

        Anyway pragmas are the solution for most of this, and we already did this with strict which changed the language considerably.

        Create something like a symlink perl7 pointing to perl and whenever the executable is run under the new name it'll activate use v7; automatically.

        Cheers Rolf
        (addicted to the Perl Programming Language :)
        Wikisyntax for the Monastery

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom