japhb Something from earlier this week ... Unicode properties that have a limited number of possible values (bits, enumerants, numeric values, etc.) have special mappings that attempt to bit-pack the field values to save in-memory space. As I recall there were various heuristics to make the mappings tighter than even that description would give, and to reduce the number of fields that crossed memory word 01:22
boundaries for runtime efficiency.
When I was hacking on ucd2c.pl, I added some more detailed debugging output for that, but it still requires some thought to make sense of it. 01:23
09:17 librasteve_ joined 12:46 nine left 12:48 nine joined 15:47 sugarbeet left 15:52 sugarbeet joined 21:54 japhb left 21:56 japhb joined