"Richard Bailey" writes:
> There is code available from my wizard at
> http://www.rtbaileyphd.com/perlwizard that is doing something fairly similar
> to what you described. Use PerlWizard to generate a simple test program,
> run it once, and then examine the contents of the pwiz subirectory, whi
. These are used in conjunction with Getopt::Long
as well.
Best Regards,
R. T. Bailey
-Original Message-
From: lee [mailto:l...@yun.yagibdah.de]
Sent: Saturday, August 30, 2014 12:09 PM
To: beginners@perl.org
Subject: Re: which module to read configuration file?
lee < <ma
lee writes:
> Hi,
>
> is there a module available to read configuration files which are like
> this:
>
>
> arbitrary_denominator-00 | alternate-denominator-00 |
> alternate-denominator-01 [| ...]
> {
> itemA =
> itemB =
> itemC =
> itemD =
> }
Following-up my own question: I found [
oblem of printing
(pre-filtered) incoming email, including the attachments, by various
criteria ("when xx sends a PDF then print it unless it has more than N
pages and print all HTML from xx, but print all PDF from xx when the
subject is "foo"; never print the PDF sent by zz and only t
From: "Chas. Owens"
I want to get some of these values (remoteProxy, the port and the IP
address
and some things more) from a configuration file. What is a good way to do
this? What is a good format for this file? Human readable and easy to
parse?
snip
I like YAML*, it is huma
On Sat, Mar 14, 2009 at 08:41, Michael Renner wrote:
> Moin,
snip
> I want to get some of these values (remoteProxy, the port and the IP address
> and some things more) from a configuration file. What is a good way to do
> this? What is a good format for this file? Human readable
);
I want to get some of these values (remoteProxy, the port and the IP address
and some things more) from a configuration file. What is a good way to do
this? What is a good format for this file? Human readable and easy to parse?
Thanks
--
|Michael Renner E-mail: michael.ren...@gmx.de |
On Mon, Dec 1, 2008 at 5:01 PM, Andreas Moroder <
[EMAIL PROTECTED]> wrote:
> Hello,
>
> I would like to parse ms .adm files. This files have a tree structure that
> look like
>
> Category Name1
> category Name2
>categor Name3
> Policy pol1
>data lines here
>...
> En
Hello,
I would like to parse ms .adm files. This files have a tree structure
that look like
Category Name1
category Name2
categor Name3
Policy pol1
data lines here
...
End policy
Policy pol2
data lines here
...
End policy
end ca
On 4/24/05, Tommy Nordgren wrote:
> I wan't links to any useful tools for generating configure scripts in
> perl.
> That is, tools to automatically generate the configure script for
> open-source
> C/C++ projects.
>
Perl itself uses a "Configure" script generated using the "metaconfig"
tool, whic
I wan't links to any useful tools for generating configure scripts in
perl.
That is, tools to automatically generate the configure script for
open-source
C/C++ projects.
"Home is not where you are born, but where your heart finds peace" -
Tommy Nordgren, "The dying old crone"
--
To unsubscribe,
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 decla
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.g
Errin Larsen wrote:
{ package Config; do "configtest.conf" }
print "$_\n" for( @Config::FILE_NAME );
Now, this code runs, and produces the expected output. However, it
also gives me a warning:
Name "Config::FILE_NAME" used only once: possible typo at
./configtest.pl line 7.
I realize I can
this:
{ package Settings; do "$ENV{HOME}/.myprogrc" }
As with a file read in using require or use, those read in using do
count as a separate and unrelated lexical scope. That means the
configuration file can't access its caller's lexical (my) variables,
nor can the caller find any
15 matches
Mail list logo
