06.07.2016, 12:56
Give me reasons why someone would prefer to use gini over other INI processors which have WAY WAY WAY more features and is WAY WAY WAY faster.
You are competing in the wrong world. Start bench-marking with y_ini or eINI. Your include provides far less features and is slower. You MUST beat y_ini in performance if you want to keep the include this simple if you WANT people to use it.
By just looking at your code, I can guarantee you that gini is AT LEAST 10 times slower than y_ini.
The only interesting feature I see is the timeout feature.
You'd do better if you would have forked the existing INI Processors and added new features to it.
strunpack? Why even save memory? Just give it away or at least keep it optional. Most servers have many GBs of memory and the memory saved by packing strings is insignificant.
Quote:
Originally Posted by Gammix
This is faster, a lot than DINI
|
By just looking at your code, I can guarantee you that gini is AT LEAST 10 times slower than y_ini.
The only interesting feature I see is the timeout feature.
You'd do better if you would have forked the existing INI Processors and added new features to it.
strunpack? Why even save memory? Just give it away or at least keep it optional. Most servers have many GBs of memory and the memory saved by packing strings is insignificant.