comment on

Would it be that hard to convert to a sane setup? Make a little script that evals each config file as shown, then YAML::Dump's it out to another replacement config file...

The calling code would (probably) be easy to replace. This would lose any comments. But you mentioned the the config file is written to in multiple places, and I can't see how the comments would be getting added anyway in that case. I have a feeling I'm missing the complexity here...

$ cat hash.conf
foo => 'bar',
baz => 'quux',

$ perl -MYAML -0 -e '%h=eval<>; YAML::DumpFile( "$ARGV\.yml", \%h)' ha
+sh.conf

$ cat hash.conf.yml
---
baz: quux
foo: bar

$ perl -MYAML -MData::Dumper -e '$h = YAML::LoadFile( shift() ); print
+ Dumper $h' hash.conf.yml
$VAR1 = {
          'baz' => 'quux',
          'foo' => 'bar'
        };
[download]

In reply to Re: "eval"ing a hash without eval by qq
in thread "eval"ing a hash without eval by Ovid

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.


We don't bite newbies here... much
	PerlMonks