Hello szabgab,
just once we play vice versa: I write and you read ;)
I dont know this being a standard, nor I know if it is wise.. but why dont use directly perl instead?
Adapting my Modules as configuration files you can have ( in modconfenv.pm ):
use strict;
use warnings;
$ENV{XX} = 42;
$ENV{YY} = 'whatever you wont';
unshift @ARGV,$_ for reverse
map {s/\s*#.*$|^\s*#.*$//; (split ' ',$_,2)}
split /\n/, <<'EOCONF'
--put here your
--list of arguments and
#any
#indented
--comment #comments
--too
EOCONF
;
print "@ARGV" unless caller;
1;
and then just perl -Mmodconfenv -e "print qq($ENV{XX} $ENV{YY})"
L*
There are no rules, there are no thumbs..
Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|