RE: Exported variables

2001-10-30 Thread Bob Showalter
> -Original Message- > From: Walter Grace [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 29, 2001 4:41 PM > To: [EMAIL PROTECTED] > Subject: RE: Exported variables > > > As a note... > > If I specify the variables in the 'use' statement (ie.

RE: Exported variables

2001-10-29 Thread Walter Grace
As a note... If I specify the variables in the 'use' statement (ie. use SI::env qw($mysqlhost $mysqluser $mysqluser $mysqlpass $db_prefix die_error);), the problem goes away. I thought the idea behind @EXPORT was to not have to do that. TIA Walter Grace At 05:22 PM 10/29/01 -0400, you wrote

RE: Exported variables

2001-10-29 Thread Walter Grace
Thanks for your answer Bob! 0-) However, I already had this set up as you describe and I am getting a "requires explicit package name" error when I try to use a variable from the module exporting its variables. There are two differences that I see between what I did and what you show:

RE: Exported variables

2001-10-29 Thread Bob Showalter
> -Original Message- > From: Walter Grace [mailto:[EMAIL PROTECTED]] > Sent: Monday, October 29, 2001 3:21 PM > To: [EMAIL PROTECTED] > Subject: Exported variables > > > > I have a variable in a module that I export (e.g. @EXPORT = > qw( $variable ); ) > > Do I have to de-reference (t