Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re^5: ${^POSTMATCH} problem

by ikegami (Patriarch)
on Jun 15, 2020 at 04:22 UTC ( #11118071=note: print w/replies, xml ) Need Help??

in reply to Re^4: ${^POSTMATCH} problem
in thread ${^POSTMATCH} problem

Short of *completely* rewriting Perl, it would have to make an actual copy to act like it was handling copies.

Replies are listed 'Best First'.
Re^6: ${^POSTMATCH} problem
by ikegami (Patriarch) on Jun 15, 2020 at 04:26 UTC

    No, it could also rewrite the call to join in terms of pre-multiconcat concatenation. I thought at first this would cause problems for magical vars, but that's not the case.

    But the point stands. To change this would impose a performance hit. Rather than slowing down join to provide more consistent behaviour, they've opted to speed up concatenation while providing less consistent behaviour. And I agree with this. In general, a programmer should never read and change a variable in the same statement. It introduces readability issues if nothing else, but it's common for it to invoke undefined behaviour.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://11118071]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (4)
As of 2022-01-17 00:50 GMT
Find Nodes?
    Voting Booth?
    In 2022, my preferred method to securely store passwords is:

    Results (50 votes). Check out past polls.