Re^2: How to call a perl function without its context?

Replies are listed 'Best First'.
Re^3: How to call a perl function without its context? by Monk::Thomas (Friar) on Jul 28, 2015 at 12:38 UTC
Basicly I want to write pure functions that will throw a compile-time error when they are not pure. Your definition of 'pure' is different from my definition of 'pure'. A 'pure' (as in functional programming) function ~can~ use external variables and still be called pure. It must not modify these variables, but it would be perfectly fine to have a sin(x) where you provide π as an external value. Changing π will change the actual output value, but if you repeat the calculation it will a) result in the same output value and b) x and π will not be modified.	[reply]
Re^3: How to call a perl function without its context? by Corion (Patriarch) on Jul 28, 2015 at 12:05 UTC
If you want to reject functions that access global state, consider what B::Xref provides you. With that, you can get at a list of global variables used by a function.	[reply]
Re^3: How to call a perl function without its context? by BrowserUk (Patriarch) on Jul 28, 2015 at 12:07 UTC
I want to write pure functions that will throw a compile-time error when they are not pure. Could you explain why? 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". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice. I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!	[reply]
Re^3: How to call a perl function without its context? by marinersk (Priest) on Jul 30, 2015 at 16:53 UTC
I'll need to check out `Safe`and its family, as they may have addressed the problem. My current thought would be to develop each function (presuming this is synonymous with a Perl subroutine in this context) initially as a stand-alone file, with `use strict;`and `use warnings;`at the top and a calling routine built in. If it compiles without errors, there are no external references. Then a quick process to extract only the subroutine into your main code and you're off to the races. The weakness is that if one bypasses the build procedure, one can violate the constraint.	[reply] [d/l] [select]