in reply to Re^3: PDL slice 2D array
in thread PDL slice 2D array

At a cost of over a hundred lines of SHOUTY code (why does your code need to SHOUT?) compared to a handful of lines of code for 1nickt's alternative. In a production context 10 times the lines of code takes at least 10 times as long to write and 100 times as long to debug. It's also mutch more inclined to suffer NIH (Not Invented Here) syndrome which significantly increases maintenance effort. So lose, lose, lose really.

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Replies are listed 'Best First'.
Re^5: PDL slice 2D array
by Anonymous Monk on Jan 21, 2025 at 08:23 UTC
    SankoR said it best: "you just enjoy letting people know you're a contrarian."
    A reply falls below the community's threshold of quality. You may see it by logging in.
Re^5: PDL slice 2D array
by Anonymous Monk on Jan 21, 2025 at 09:05 UTC
    So lose, lose, lose really.
    Essentially. Portable, reliable and critically as far as any time based functions goes accurate code is infinitely preferable over a hodgepodge of unnecessarily hard to read ( $O, seriously? ) overly verbose spaghetti, which is neither portable nor reusable.