On Thu, 30 Sep 2004 23:30:16 +0200, Gunnar Hjalmarsson <[EMAIL PROTECTED]> wrote: > > Nothing prevents you from declaring @FILE_NAME: > > package Config; > our @FILE_NAME; > do "configtest.conf"; > print "$_\n" for @FILE_NAME; > > -- > Gunnar Hjalmarsson > Email: http://www.gunnar.cc/cgi-bin/contact.pl
doesn't that kinda defeat the purpose of declaring the Config name space? I was trying to keep the variables in the configtest.conf file in a different name space than the main program. I don't HAVE to do this, just thought it seemed like a good way to keep the two, potentially conflicted, name spaces apart. I wanted to see the variables created in the Config name space require a dereference (is that the right word?), ala Config::FILE_NAME. That way, if the main code ALSO has a FILE_NAME variable, the contents of the (at run time, unknown to the main developer) config file. I hope that's making sense. --Errin -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
