I think that the nifty thing in this example is that they *can't* know anything about it.
On the contrary, if you're loading their Perl code into your process, they can find out just about anything.
For example, they could supply you with a module with a BEGIN block that walked through all of the package namespaces, dumping out subroutine names and variable values. They could also wrap relevant subs in a logging wrapper to observe the flow of function/method calls and the arguments they receive, dumping the results to a text file for later review.
In an extreme case, they might even be able to deparse your program back to source code using something like the B:: modules.
However, I agree that in the vast majority of cases, most people won't do any of the above, and your commercial application will be sufficiently safe. (To the best of my knowledge, nobody else ever used the plugin mechanism in IntraNetics other than in the specific ways we documented.)
In reply to Re: Re: Re: Win32 binary (and extensible) OO-perl applications
by simonm
in thread Win32 binary (and extensible) OO-perl applications
by dpmott
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |