[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)

danpetry notifications at github.com
Tue Jan 29 18:46:13 CET 2019


danpetry commented on this pull request.



> +Modules should be abstracted from one another as cleanly as possible. It should
+be easy for users to manage or exploit this modularity, for example through
+configuration methods, easy integration of third-party source code, or
+different levels of modularity. The granularity of modules should be stable and
+similar across different types of module. Users shouldn't want to split
+modules, but they shouldn't be unnecessarily fine-grained either.
+
+## Cross-hardware portability
+
+Users might want to write a program for one piece of hardware, and later run it
+on another. RIOT should let user code be completely portable, so long as it's
+valid with the hardware.
+
+The hardware abstraction layer should be stable, well defined and consistent.
+Above the HAL, the only thing that modules should know about hardware is
+whether a required feature is there or not. If it isn't, the module should

This is meant to suggest that the modules should only know about whether their dependencies are compiled for that hardware. Perhaps "whether its build dependencies are provided or not"?

-- 
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/10162#discussion_r251943453
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190129/77e0e06b/attachment.html>


More information about the notifications mailing list