Errin Larsen wrote:
Gunnar Hjalmarsson wrote:
Nothing prevents you from declaring @FILE_NAME:
package Config;
our @FILE_NAME;
do "configtest.conf";
print "$_\n" for @FILE_NAME;
doesn't that kinda defeat the purpose of declaring the Config name
space?
Can't see how. It is being declared within package Config.
I was trying to keep the variables in the configtest.conf file in a
different name space than the main program.
That sounds wise, and I didn't suggest anything else.
I wanted to see the variables created in the Config name space
require a dereference (is that the right word?),
No. You mean require the fully qualified names.
ala Config::FILE_NAME.
If you don't export anything from package Config, you still need to
use the fully qualified names when calling those variables from other
packages, so I don't think that's a reason either to not declare the
variables in package Config.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
