> At the very worst, I can ship a PAR::Filter::Bleach as an example of > input filtering, along with PAR::Filter::PodStrip.
Sounds like a nice idea, especially due to the risk of inadvertent side-effects from Acme:Bleach (See below) > Oh, and another question for list members. If I say: > > pp -f Bleach foo.pl > > should pp apply Bleach to foo.pl only, or to all modules it requires? > Should we ad another -F switch to mean "filter dependencies", so one > can say: I think due to the rather destructive nature of Bleach, having a switch and a modified version would be rather nice. Perhaps for example someone would find that it causes some problem with one module but not another. To me, it seems rather rude to hide source that was written by someone else, but it doesn't seem to be easy to determine which code was written and which borrowed, so I guess leaving it to the authors discretion would be ok... Ultimately though, I suspect that the commercial authors won't be happy until they have something equivalent to the PHP type encryption technique where the encrypted code can be loaded straight into the interpreter, and it's only decoded there. This obviously requires a modification to the runtime engine (or support from). This can obviously still be defeated, but it seems to have been a substantial obstacle in practice.
