I agree that there are several interesting aproaches to standarize config files. I also prefer the Apache config way. OTH, I should better prefer an XML way. I know.
But this is similar to what I use in my personal config files. And in this OO way, I won't feel guilty when keeping on doing so, programatically. It is error prone!
I should only point out that it is not possible to keep a special order in the variables, because of the hash nature of these config files.
But it is Ok for me and my scripts :)
| { | \ | ( | ' | v | ' | ) | / | } | ||||||||||||||||||||||||||||||
| ( | \ | _ | / | ) | _ | _ | _ | _ | ` | ( | ) | ' | _ | _ | _ | _ | ||||||||||||||||||||||
| ( | = | ( | ^ | Y | ^ | ) | = | ( | _ | _ | ^ | ^ | ^ | ^ | ||||||||||||||||||||||||
| _ | _ | _ | _ | \ | _ | ( | m | _ | _ | _ | m | ) | _ | _ | _ | _ | _ | _ | _ | _ | _ | ) | c | h | i | a | n | o | , | a | l | b | e | r | t | o |
In reply to Re: Reading and Writing Perl Config Files
by chanio
in thread Reading and Writing Perl Config Files
by jdhedden
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |