Page 2 of 2

Re: Test a section/key entry in .ini for existance

Posted: 04 Mar 2023 12:57
by PeterH
Just an idea
(or name it a 3rd level wish)

You describe suffering performance on getting just single keys in XY-algorythm.

Couldn't it be possible to make it better by allowing to request multiple keys for XY-type? That is, for key= allow a list of keys, and the return will be a list of values. (Each of those could be the error-indicator for missing key etc.)
Problem might be the separator - it may not appear in any value. Could be resolved by using XY's modern :ugeek: arrays!
For compatibility of return-type: if a list is requested, it must be specified as an array. Only then an array is returned.

But as said: just an idea. Though would be an 'official' use for XY's array! :whistle:

Re: Test a section/key entry in .ini for existance

Posted: 04 Mar 2023 13:39
by admin
Is this an academic question or are you really suffering from performance issues here?

Re: Test a section/key entry in .ini for existance

Posted: 04 Mar 2023 16:24
by PeterH
This question was just the combination of the info in help about (performance &) your use to mass-read keys, and my idea to read multiple keys.

But no performance problems seen, and no really need. Only "nice to have".
If it's much work/time: just forget it - no problem at all.