Timeline for Simple key-value store in C
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jul 7, 2016 at 12:56 | comment | added | buddy | Synchronisation protection you can add to make it thread safe. | |
| Sep 21, 2014 at 18:07 | vote | accept | Dagg | ||
| Sep 20, 2014 at 22:09 | answer | added | vnp | timeline score: 2 | |
| Sep 20, 2014 at 20:48 | answer | added | André Sassi | timeline score: 6 | |
| Sep 20, 2014 at 17:56 | comment | added | Mat | Then make it an opaque struct. (I don't really buy the on-stack use-case, you're going to be doing a dynamic allocation anyway.) | |
| Sep 20, 2014 at 17:22 | history | edited | Dagg | CC BY-SA 3.0 |
added 108 characters in body
|
| Sep 20, 2014 at 17:04 | comment | added | Dagg | @Mat the user should never be messing with length or pairs in the use cases I have in mind, so it seemed like the thing to do. Maybe it's overkill, though. | |
| Sep 20, 2014 at 14:46 | comment | added | Mat | "I'd like to make the length and pairs fields in KVSstore read-only with const" - why do you want to do that? | |
| Sep 20, 2014 at 10:36 | history | asked | Dagg | CC BY-SA 3.0 |