[quoted lines by Samuel Thibault on 2021/05/08 at 22:07 +0200] >I however eventually digged back into the git log, and this isArray >was really introduced to determine, as documented, whether there is >to be possibly several values, or always one. That's notably used in >the Python bindings to know whether it shall return, when one value >is returned, an array of one value or directly the value. That's >contradictory with what you wrote above.
Well ... retrospection isn't a bad thing. It's kind of like when a politician changes his/her mind on some important issue. Some think it shows weakness of character and others think it shows thoughtfulness and a willingness to acknowledge a past wrong. :-) In this case, yes, I do think my former opinion was wrong. I now think that the count should mean the size of a single entry, and that the isArray flag should mean either exactly one entry (false) or zero or more entries (true). This, of couse, would be not backward-compatible, and would mean bindings changes. -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 | _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
