[riot-notifications] [RIOT-OS/RIOT] gcoap: API revamp - Abstracting nanocoap (#16855)

chrysn notifications at github.com
Thu Sep 16 10:58:40 CEST 2021


One detail: I'd rather think that the getter/setters would first be introduced in nanocoap (static inline; we have `coap_code` and would gain `coap_set_token` (or _rebuild_header? will become clear from usage)).

Then, we'd see which of these can have trivial wrappers (technically all b/c gcoap-1.0 is not going away from nanocoap) that just cast-and-call (again all static inline, so in the end it's member access again), and which access members that are now moved.

-- 
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/issues/16855#issuecomment-920718638
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210916/d381d3d4/attachment.htm>


More information about the notifications mailing list