[riot-devel] Include folder in net / RPL restructuring
Martin.Landsmann at haw-hamburg.de
Thu Jan 30 12:31:29 CET 2014
Von: devel [devel-bounces at riot-os.org]" im Auftrag von "Martin Lenders [authmillenon at gmail.com]
Gesendet: Donnerstag, 30. Januar 2014 12:15
An: RIOT OS kernel developers
Betreff: Re: [riot-devel] Include folder in net / RPL restructuring
I think Fabian meant the already existing directory ``sys/net/routing_layer/``.
Though they might not be used by anything else but the routing layer, I think it is most clearly to put the function prototypes into sys/net/include/etx.h and the implementations into sys/net/routing_layer/etx/. In the optimal case all the other headers in there would be used by their respective upper or layer protocols, too, and experience showed that moving the implementation around later-on (e.g. to rename routing_layer to forwarding_layer ;-)) is heavily simplified, when public headers are not in those directories.
2014-01-30 Landsmann, Martin <Martin.Landsmann at haw-hamburg.de<mailto:Martin.Landsmann at haw-hamburg.de>>:
A subfolder to organize the common used functions sounds good to me. Especially when they are probably used across distinct routing protocols .
Im not sure about the name routing_layer, it sounds a little bit too general.
I would propose e.g. forwarding_layer.
Von: devel [devel-bounces at riot-os.org<mailto:devel-bounces at riot-os.org>]" im Auftrag von "Fabian Brandt [fabbrandt at googlemail.com<mailto:fabbrandt at googlemail.com>]
Gesendet: Donnerstag, 30. Januar 2014 10:32
An: devel at riot-os.org<mailto:devel at riot-os.org>
Betreff: [riot-devel] Include folder in net / RPL restructuring
for restructuring RPL I was wondering where to put common Routing Layer functions like ETX. My first and obvious impression was to move them in the subfolder routing_layer, but it is also possible to put such functions into the include folder of net directly. Any suggestions?
Have a nice day
devel mailing list
devel at riot-os.org<mailto:devel at riot-os.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel