The read command can take a word argument, e.g.
read 0,WORD w4
The manual says "When word variables are used (with the keyword WORD) the two bytes of the
word are saved/retrieved in a little endian manner (ie low byte at address, high
byte at address + 1)". Fine.
Now consider the converse problem: using the EEPROM command to load the memory with word data. It seems I cannot say something like
EEPROM 0,(1, 2, WORD 12345, 6, 7)
It's possible that if I said
EEPROM 0,(1, 2, 12345, 6, 7)
that Basic would compile the 12345 as two bytes. But then, if the word value I actually want to enter is less than 256, I'd have to remember to insert a 0 byte.
read 0,WORD w4
The manual says "When word variables are used (with the keyword WORD) the two bytes of the
word are saved/retrieved in a little endian manner (ie low byte at address, high
byte at address + 1)". Fine.
Now consider the converse problem: using the EEPROM command to load the memory with word data. It seems I cannot say something like
EEPROM 0,(1, 2, WORD 12345, 6, 7)
It's possible that if I said
EEPROM 0,(1, 2, 12345, 6, 7)
that Basic would compile the 12345 as two bytes. But then, if the word value I actually want to enter is less than 256, I'd have to remember to insert a 0 byte.