Thanks for putting me onto PAR looks like and interesting project. Hmmm, see what you getting at re: xsp pages, am I correct in thinking that simply speaking, AxKit / TaglibHelper 'simply' fills in calls to a tag, within a taglib with the relevant code and then throws the result at the Perl interpreter?
All comes back to there being no real way of securing the Taglib, that wouldn't stop a half decent Perl programmer from ripping the source. The same holds for most complied programs to some degree, but any improvement on our existing methods of obfuscation is welcome in regard to our current project. Cheers, Marc. On 24/3/05 6:48 pm, "Christian Jaeger" <[EMAIL PROTECTED]> wrote: > Why not use the bytecode compiler instead, or PAR::Filter::*. > > But I guess the real question is what to do with xsp files which > defer perl code generation to load time. > > Christian. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
