in reply to Suggestions for design of a config/rules file

The node Persistence for options has a discussion of a similar requirement. At that time, I chose XML::Simple to store configuration information. This could have been better, since non-programmers needed to change the file, and editing XML by hand was not as simple as they would have liked.

For my current project I am using YAML, which is working very well.

It should work perfectly the first time! - toma
  • Comment on Re: Suggestions for design of a config/rules file