AndyLindsay
commented
8 years ago Thanks for the contribution. I did something similar when I first wrote them, using n = 0 for zero terminator. I also used a negative bytecount to set the maximum number of characters that would be allowed if the zero terminator was not reached. The negative values didn't seem like a good idea from the API standpoint, and I don't remember why I also decided to remove the zero terminator.
Looking at it now, I think it'll be worth a try, but it will need some extra work first.
Instead of a fixed value of 128, please add a function that configures a global variable that holds a byte count. The n=0 behavior would then go up to that byte count or c = 0, whichever comes first. I would recommend making the default 64 bytes since that's the size of the default serial buffer. (or is it 63... I don't remember; please check.) Please also update the documentation for the modified functions and the new one and make sure to test rigorously.
Here are some naming ideas.
int eeprom_zstrMaxCount; ee_zstrMax(int maxCount){}
zfi
MatzElectronics
Allow user to set the str length to zero - and have the function auto-detect the string length using the null terminator. The string, including the null terminator is written to and retrieved from EEPROM.