in reply to odd things with my and our

As for the error you are receiving about the use of our(), I'm going to assume you are using an older version of perl in which our() was not yet introduced (or else an extremely new version where our() has suddenly become deprecated (which I highly doubt)). Though I wonder why the error message includes the part about deprecation. Wouldn't/shouldn't it just complain about a reserved word and not about deprecation? Just going by the English language, in which 'deprecated' means that the behaviour is being phased out, being replaced by a newer behaviour.

Replies are listed 'Best First'.
Re: Re: odd things with my and our
by jcpunk (Friar) on Jan 25, 2004 at 05:59 UTC
    I am using an old version of perl (which i cannot avoid) but the part about deprecation made me think that the sysadmin finally upgraded it without my knowlege to some weird perl6 beta or something odd like that, but with some proding (I dont have shell access to the machiene, just ftp) I was able to coax this out of it
    This is perl, version 5.005_03 built for i386-linux
    Copyright 1987-1999, Larry Wall

    Perl may be copied only under the terms of either the Artistic License or the GNU General Public License, which may be found in the Perl 5.0 source kit.

    Complete documentation for Perl, including FAQ lists, should be found on this system using `man perl' or `perldoc perl'. If you have access to the Internet, point your browser at http://www.perl.com/, the Perl Home Page.

    So that is indeed odd and looks like use vars and I are going to have to get aquanted.

    sadly this computer just landed itself under my dominion and it is a bit different on that version of perl.
    thanks for the help.


    jcpunk
    all code is tested, and doesn't work so there :p (varient on common PM sig for my own ammusment)
[reply]

In Section Seekers of Perl Wisdom