colin_e wrote:
Cool. To my (naiive i'm sure) eye this looks just like the behaviour of a brace-delimited
block in a chunk of mainline code, which is what I was hoping/expecting.
(I guess you are talking about lexicaly scoped vars) plus that any globals which in a normal script:
$foo = 5;
will end up in main:
$main::foo
will be nuked as well.
Well, keep in mind that <Perl> directives are now processed in a very similar way other 'phases' are dealt with, so internally, each <perl> block get's it's own package name. That's what gets wiped after the <perl> block is finished being evaluated. So if you stick something in a explicit package name, like $main::foo = 1, that will remain.
Some examples of good/bad/dangerous things to do in these <Perl></Perl> sections
would be very helpful though. I can imagine for instance that mucking around with
package declarations inside one could make life complicated.
It's more simple than that. don't use <Perl></Perl> sections for anything that you can do from real perl. <Perl></Perl> sections are there only for doing Apache configuration. Anything else, you are on your own. so any example that doesn't deal with Apache config is a bad example.
-------------------------------------------------------------------------------- Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5 http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5
signature.asc
Description: OpenPGP digital signature
