in reply to Re^4: RFC: pragma pragmatic
in thread RFC: pragma pragmatic

to prevent imported functions from being accidentally called as methods by a class's user

I would have thought the automatic provision of the object handle as the first parameter would elicit sufficient errors to make tracking down the error/typo reasonably easy.

(BTW: Good to see you back around.)


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit

Replies are listed 'Best First'.
Re^6: RFC: pragma pragmatic
by chromatic (Archbishop) on Aug 11, 2017 at 00:33 UTC

    Yeah, it always felt like more of a theoretical problem than a widespread one, given the pervasiveness of the function/method conflation in Perl. Perl's just not built for that kind of safety.