Semantic differences between save/write/store and read/load?
load, save, store
Solution
Well, it is up to you. I personally use `saveXXX()` and `loadXXX()` for most of such code and it's quite not important how the data is saved technically (file, DB etc). From application point of view it makes no difference. Code that saves just needs data to put it in the storage, more or less persistent, and it does not really bother how it is done by the storage layer. I simply suggest to stick to one naming, basically for sake of simplicity and consistency.
Problem
I never know what is the correct name for a function that writes/stores/saves something in a file. When should I use `save()` vs `store()` vs `write()` and what is the difference in meaning between those? I guess `store`is used if I write to a database, `write`for text files and `save`for binary data, is that correct? What about XML files?