[riot-notifications] [RIOT-OS/RIOT] RFC: Change of sensor and actuator API & auto initialization (#11826)
notifications at github.com
Mon Jul 15 14:29:21 CEST 2019
> I'm not sure if I understand. This is a foo-device specific function, right? Then how does this work together with app allocated dev/param variables? Or is this only meant for (currently) auto-init allocated devs?
Excatly. If the use wants to access an auto-initialized device by its index, I would like to provide a static inline function to access the array element. (For non-auto initialized devices, the user will pass the pointer to the manually initialized device descriptor directly, instead of calling `foo_get_dev()`.)
> But I'm against expressing parts of this configuration as modules and other parts with custom blacklist defines like #ifndef NO_AUTO_INIT_FOO. As currently modules are the way to include specific functionalities I'd say it's would be more consistent to stick with that. What would be the big problem with having "tons of modules" anyway? I don't think that this will add excessive complexity to the build.
You're right. I didn't think it through: E.g. `make info-modules` will only list the modules actually *used*. So my fear that too many *available* modules will be confusing/overwhelming is pointless.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications