Re^3: Problems with 'our' definition with perl 5.00503

Ok, almost there
The project is a constant work in progress, most of the our definitions could be changed to my, but will need our in the future. All 'our's that need to be global right now have a corrosponding VARS placement so that shouldn't cause any problem.

I'm not using strict at this stage in this particular script. That code looks almost like what I need, but without referencing my on any our calls.
The main errors I'm getting is something like this:-
"our %hash;" - error illegal modulas of 0. Because our isn't defined it's treating % as a modulas.

I'm sure the solution is quite simple, I just don't quite know how to do it.
The host has got back to me saying the server is part of a nest and they don't want to upgrade all of them, but I'm still trying.

Thanks in advance.

Comment on Re^3: Problems with 'our' definition with perl 5.00503

Replies are listed 'Best First'.
Re^4: Problems with 'our' definition with perl 5.00503 by tilly (Archbishop) on Jun 30, 2005 at 17:06 UTC
If you have a corresponding VARS placement, then you should definitely not be using our, and if you don't need it to be global then you should also not be using our. Just because the feature exists does not mean that it is appropriate. See Why is 'our' good? for some arguments that may convince you to solve your problem by using our less.	[reply]