Hmm, that's not expected behavior with the code you're showing here. Are
you running this under ModPerl::Registry? It's supposed to generate a
unique package name for every file that prevents subs from colliding.
There are some things to watch out for when using subroutines in code you
run under
On 08/01/2017 12:45 PM, John Gigawatt wrote:
> * Is there a way, when defining "sub testSub" to force it to be locally
> scoped? I believe the equivalent with variable is to say "our" rather than
> "my"... but not sure how that would happen here.
do you know what package scopes are?
--
So
On 08/01/2017 12:45 PM, John Gigawatt wrote:
> One solution obviously has been to make sure I have a custom name for every
> subroutine... but that can get messy to maintain and is not perfect.
Johnie Giggawatt?
give me a break
--
So many immigrant groups have swept through our town
that
Hi,
I have a question on the best way to handle having multiple "web pages"
having a subroutine with the same name in it. I apologize in advance if I
use the wrong terminology. I know there are issues with library modules
(use, etc) and also global variables. I am assuming this is similar but
