in reply to RFC: config::simple vs config::ini

Erm ... why???

I mean, configs are in general small and loaded just once so the time spent loading and parsing the data is 1. negligible and 2. mainly the time it takes to read the data from the hard drive/network if it's not already in cache. It might make some tiny sense to measure the access to the already read data, but the loading itself is best left outside the benchmark.

I do believe the choice of the config reader should depend only on the format of the config file and the API it provides. Anything else is a premature microoptimization which is as we all know the root of all evil.

Jenda
Enoch was right!
Enjoy the last years of Rome.

Replies are listed 'Best First'.
Re^2: RFC: config::simple vs config::ini
by thanos1983 (Parson) on May 21, 2014 at 10:44 UTC

    To: Jenda,

    You are right most of the time the *.ini files are loaded just once. The reason that I implement this experiment is that I wanted to become familiar with all possibilities of parsing data through *.ini and secondary some times I am creating while(sleep 1) loops with scripts that include MySQL syntax. In such cases again it does not make a big difference, but I thought it would be fun to apply and find the most suitable solution to my needs.

    In conclusion, I did not find any documentation that could include all of them together. So I thought why not write something by my self experiment and contribute to least possible degree.

[reply]

In Section Meditations