Addition needed to EEPROM.read() description

It appears that the the return value for EEPROM.read() is -1 if the memory location has not been written to first.

Didn't see it mentioned in the referance.

I added it. Thanks.

In fact, as bytes are stored as unsigned char, the value 255 is more correct.. 0xFF will make everybody happy..

Franky is right, although it's not so much that the bytes are "stored" as unsigned char as that EEPROM::read() is prototyped to return unsigned char.

And just to be clear, the 0xFF return value is not some special code issued by the library meaning "this byte has never been written". It's just that EEPROMs are (mostly) delivered with each byte preprogrammed to 0xFF.

Mikal