[quoted lines by Samuel Thibault on 2021/05/11 at 01:11 +0200] >I'm also thinking that we could as well just squash the fields isArray >and hasSubparam into a flags field, since we also want to add can_read >and can_write, and possibly others in the future. We can make it a 16bit >field and make isarray bit 0 and hasubparam bit 8. That copes with ABI >compatibility on little-endian platforms, which is probably all that we >really care about concerning any potential use of brltty 6.3.
Yes. I tend to prefer the uint16_t :1 syntax, because it makes the code cleaner, but, for now, that'd require a lot of filler fields to make hasSubparam be the eighth. -- 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
