Re^2: Another Subroutine Redefined Post

Rather than posting an entire script (because I don't have a small example), here's another thought to mull over...

In one particular case, the error "subroutine X redefined at ..." appears only sometimes. I was able to duplicate it, not by refreshing my page, but by navigating back and reclicking the link.

Could this have something to do with a previously-loaded subroutine in my server process' memory that's being redefined?

Comment on Re^2: Another Subroutine Redefined Post

Replies are listed 'Best First'.
Re^3: Another Subroutine Redefined Post by JadeNB (Chaplain) on Nov 24, 2009 at 16:51 UTC
I'm a little confused—you say “I could post an actual subroutine”, but then say that you don't want to post a code snippet? Anyway, I think that it's important to realise that Perlmonks are happy to give you all the help we can, but that you have to show that you're willing to meet us halfway—saying “I won't take the effort to make a small code sample, but you should take the effort to guess why a problem might be occurring anyway” isn't likely to lead anywhere useful.	[reply]
Re^4: Another Subroutine Redefined Post by Heffstar (Acolyte) on Nov 25, 2009 at 16:00 UTC
In actual truth, I'm having a hard time finding a script that's small enough to post. Posting a single subroutine would probably not help. The "smallest" is ~1000 lines. I will make another attempt to find a script that is suitable, but it may be a little while... thanks for the will to help; it really is appreciated. On your earlier comment, you mention throwing away the "&" on my sub calls because it's the old convention. Aside from being more modern, are there other benefits of doing so? A side note about these errors... after making some code changes, I'll attempt to run the script and good ol' "Internal Server Error" rears it's ugly head (I guess that happens sometimes eh?). I'll fix the error and upon refreshing the page and rerunning the script, every single subroutine I've got defined in my script will show in the logs as redefined. Yet further refreshes WON'T cause them to appear as redefined. Server cache maybe?	[reply]