@Hippy
Does this mean the table is another independent memory area of 256 bytes in addition to the eeprom and scratchpad, or does it use program space?
Manual2 refers to the "scratchpad", and "embedded lookup table", and "within the program" for the readtable command, and to the "eeprom" for the table command - not too clear to me. My best guess is that this table will be created in ram and take up program memory space - can you confirm?
It seems that using @ptr, @ptrinc/dec is faster than read eeprom and you can also do more with them like the inc/dec compared to eeprom.
Where does the table construct fit into the scheme of things?
Just created a table starting at 0 in an existing program with a 30 char text string and the syntax checker says the program size grew by 30 bytes.
Created a second table the same but stating at 200 and it took another 30 bytes.
I guess this means it is as suspected - table is created in ram in the program memory space. Niether scratchpad nor eeprom are changed when the table is created.
In the simulator, the table creation is instantaneous like it is for the eeprom setup i.e. the lines are just jumped over, there is no progress step by step along the text string as there is for many other commands so presumably this could be quite fast and therefore could be used within the program to update the table contents from time to time if the table is not large enough for everything at once.