[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)

José Alamos notifications at github.com
Thu Jan 10 15:24:40 CET 2019


jia200x commented on this pull request.



> +typedef struct {
+    char name[DUMMY_MAX_NAME_LEN];
+    char val[DUMMY_MAX_VAL_LEN];
+} dummy_store_storage_t;
+
+
+/* This will be our "storage device" */
+dummy_store_storage_t dummy_store[DUMMY_STORE_CAPACITY];
+
+static int registry_dummy_load(registry_store_t *store, load_cb_t cb,
+                               void *cb_arg);
+static int registry_dummy_store(registry_store_t *store, const char *name,
+const char *value);
+
+/* Storage Facility descriptor to be registered in the RIOT Registry */
+static registry_store_itf_t interface = {

> Otherwise the implementer might take the code and diagram as guidance and see that there's a discrepancy, and be left wondering which to implement

Honestly I don't see why we should state a very specific implementation detail in the RDM.
Static descriptors can indeed be registered in C. We do it all the time (e.g [netreg entries](https://github.com/RIOT-OS/RIOT/blob/68dc5b0d6e0422df9c3653c2cb8021fc35974aae/examples/gnrc_networking/udp.c#L128) )


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10622#discussion_r246777026
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190110/d1a11ede/attachment.html>


More information about the notifications mailing list