Feature-request: split the strings.xml for in-device and settings related strings

Each module scope variable takes 16 bytes in the data segment. That's fixed overhead whether you call loadResource or not. Then I'm guessing the resource table has 8 bytes per resource, but only gets allocated on the first call to loadResource. Which would give 24 bytes per resource. 

Each module scope variable takes 16 bytes in the data segment. That's fixed overhead whether you call loadResource or not. Then I'm guessing the resource table has 8 bytes per resource, but only gets allocated on the first call to loadResource. Which would give 24 bytes per resource. 

Each module scope variable takes 16 bytes in the data segment

I misremembered this. It's actually only 8 bytes. The symbol is stored in 3 bytes, there's a flag byte (indicating data type amongst other things), and then 4 bytes for the value (which in this case is just a Number). So presumably the resource table uses 16 bytes per string. I guess it needs address, length, id, and something else?

maybe 24 but memory monitor shows data only in kB...

why????