08.05.2015, 15:04
eINI is not even close to any of them INI Processors you mentioned.
Every single line of eINI was written by me.
The only thing in common with y_ini and eINI is they both use Linked Lists which by far is the best way to store INI Data.
dini,sii and eINI are at two different ends.eINI is 40x faster than dini.
dini,sii both do not support sections/tags whereas eINI supports.
y_ini has half the features which eINI provides.
Performance of all these INI Processor when compared with eINI differ significantly except for y_ini.
I was wondering if I need to break this thread up and make two separate tutorials, one for reading and one for writing in the tutorial section.
This is from 2013, I just spent around 10-12 hours on updating this.
This is anyway the fastest INI Processor I believe if my speeds tests are valid.
Do you use SQLite even for storing languages?I use INI to store languages with tags like [en],[fr]...
Every single line of eINI was written by me.
The only thing in common with y_ini and eINI is they both use Linked Lists which by far is the best way to store INI Data.
dini,sii and eINI are at two different ends.eINI is 40x faster than dini.
dini,sii both do not support sections/tags whereas eINI supports.
y_ini has half the features which eINI provides.
Performance of all these INI Processor when compared with eINI differ significantly except for y_ini.
I was wondering if I need to break this thread up and make two separate tutorials, one for reading and one for writing in the tutorial section.
Quote:
Me too I prefer Sqlite, and I think if anyone really requires to use some of the features in this they would be using a plugin just feels like this tries to re-invent the wheel which is fine but was it really worth the effort?
|
This is anyway the fastest INI Processor I believe if my speeds tests are valid.
Do you use SQLite even for storing languages?I use INI to store languages with tags like [en],[fr]...