You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
-
Exactly: the ability to retrieve previously stored strings and the ability to temporarily store strings. The pubs I made is to give you some head start of the logic... I wanted to explore the techniques/logic in a higher lever environment. An intermediate layer is the management of the memory, and the bottom layer / foundation is the actual device driver. The basic functions are:
- write(string) returning ID (addr)
- read(addr) returning string
- update(addr,string) returning nothing
- delete(addr) returning deleted
- writeKeyed(key,string) returning ID (addr) --- key is a string
- readKeyed(key) returning ID (addr) [and string]
- [updateKeyed(key,string)]
- [deleteKeyed(key) returning ID (addr) [and string]
The functions in [square brackets] are just combinations of non-bracketed ones.
- write(string) returning ID (addr)
allObjects
@DrAzzy - sorry, I got the parts and couldn't wait: http://forum.espruino.com/conversations/260971/
I'd be interested to see if it works for you?
@allObjects - this is what I meant... So ideally you'd have two parts: One that accesses the EEPROM/FRAM/MRAM/etc, and another that handles storage and memory management of objects - so that for instance you could use your memory manager on @DrAzzy's EEPROM.
Hopefully when we've got a few memory drivers that work the same way, we can maybe pull your code into a module that will work with them?