[riot-notifications] [RIOT-OS/RIOT] SAUL: Introduce undefined value (#11446)
notifications at github.com
Fri Apr 26 09:21:25 CEST 2019
> Mmmm... the problem with this approach it that is assumes that there always exists a specific value that can be used to represent "undefined", which may not be the case.
That's true, but for instance, the SAUL shell command already assumes this, and worse, it assumes the value. So I figured we should have some sort of formal way of doing defining this.
> Also, how can a device signal that it does not support and undefined value?
The one proposed here is only one of the posible solutions. We may also consider passing somehow a mask to the `write` function, to ignore specific positions? Any other ideas?
> Maybe this could be solved by presenting the same physical device as multiple SAUL devices.
I'm not sure about this, specially if you are thinking about saving memory, having multiple entries on the registry to expose the same device in different ways, just because the interface does not cover all the use cases.
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