Re: Re: parsing arguments

I was going to suggest Config::IniFiles myself...

use Config::IniFiles;
my $config = Config::IniFiles->new(file=>'asdf.ini');
my $someParam = $config->val('section','param');
[download]

where asdf.config would look like

[section]
param=value
[download]

----
Zak

undef$/;$mmm="J\nutsu\nutss\nuts\nutst\nuts A\nutsn\nutso\nutst\nutsh\
+nutse\nutsr\nuts P\nutse\nutsr\nutsl\nuts H\nutsa\nutsc\nutsk\nutse\n
+utsr\nuts";open($DOH,"<",\$mmm);$_=$forbbiden=<$DOH>;s/\nuts//g;print
+;
[download]

Comment on Re: Re: parsing arguments Select or Download Code

Replies are listed 'Best First'.
Re: parsing arguments by b10m (Vicar) on Oct 08, 2003 at 11:19 UTC
I'm not too familiar with Config::Inifiles, but from your example, it doesn't seem to fit mifflin's needs, since (s)he wants to parse command line arguments, and Config::Inifiles works with, tada Inifiles :-) Since the Getopt::Long was already mentioned, I'd like to add "AppConfig". I have been using that myself recently and must say it works nice. It parses command line arguments, aswell as configuration files. -- B10m Edit: English can be hard sometimes :-(	[reply]
Re: Re: parsing arguments by zakzebrowski (Curate) on Oct 08, 2003 at 18:18 UTC
Indeed, you are correct. However, in the spirit of "there's more than one way to do it", I provided the link to the module... Cheers ---- Zak `undef$/;$mmm="J\nutsu\nutss\nuts\nutst\nuts A\nutsn\nutso\nutst\nutsh\ +nutse\nutsr\nuts P\nutse\nutsr\nutsl\nuts H\nutsa\nutsc\nutsk\nutse\n +utsr\nuts";open($DOH,"<",\$mmm);$_=$forbbiden=<$DOH>;s/\nuts//g;print +;` [download]	[reply] [d/l]
Re: Re: Re: parsing arguments by mifflin (Curate) on Oct 13, 2003 at 19:27 UTC
Thanks for posting your reply on Config::IniFiles. Although it did not solve the problem I was having in thread I have installed in my system and have started using it. I love it! Thanks again.	[reply]