Re: Perl

> Take a step back from things, and let the code be code, and the data
> be data? (vs. doing the "data as code"?) (i.e. define a format for
> a configuration file, and read+parse that file to build up %networks )
>
> Once you decide on a format for the config/data file, it'd be easy to
> write a perl script to convert your existing "data as code" into just
> the necessary data bits :)

Right, thats why I was looking for a simple config module to use.
Though none of them seem to be able to do nested hashes.

So yeah instead of writing some code to create perl code, it might be
easier to write some code to make my own config module.

It looks like Config::General might be able to do what I want.
Received on Thu Jul 20 17:14:24 2006