Re: catching undefined global variables

2004-04-19 Thread Dirk Koopman
On Mon, 2004-04-19 at 16:59, Nick Ing-Simmons wrote: > Dirk Koopman <[EMAIL PROTECTED]> writes: > >> > > >> >$SBOL::ACCNO = $SYUS::LOGNAME; > >> > >> What doesn't exist? You have two packages and a variable in each package > >> there which of the four exist to perl. > > > >I express myself badly (

Re: catching undefined global variables

2004-04-19 Thread Nick Ing-Simmons
Dirk Koopman <[EMAIL PROTECTED]> writes: >> > >> >$SBOL::ACCNO = $SYUS::LOGNAME; >> >> What doesn't exist? You have two packages and a variable in each package >> there which of the four exist to perl. > >I express myself badly (not unusual). Yes, the variables exist and, even >with strict on, cau

Re: catching undefined global variables

2004-04-19 Thread Dirk Koopman
On Mon, 2004-04-19 at 10:46, Nick Ing-Simmons wrote: > Dirk Koopman <[EMAIL PROTECTED]> writes: > >I am interfacing to an ancient 4(ish)GL library. It defines a number of > >tied (global) variables which are defined internally to the library but > >are not (necessarily) yet defined in perl. > > > >

Re: catching undefined global variables

2004-04-19 Thread Nick Ing-Simmons
Dirk Koopman <[EMAIL PROTECTED]> writes: >I am interfacing to an ancient 4(ish)GL library. It defines a number of >tied (global) variables which are defined internally to the library but >are not (necessarily) yet defined in perl. > >So we have some code that looks like this:- > >use FF; > >$SBOL::

catching undefined global variables

2004-04-16 Thread Dirk Koopman
I am interfacing to an ancient 4(ish)GL library. It defines a number of tied (global) variables which are defined internally to the library but are not (necessarily) yet defined in perl. So we have some code that looks like this:- use FF; $SBOL::ACCNO = $SYUS::LOGNAME; This are variables which