[riot-notifications] [RIOT-OS/RIOT] Question: Where does the `#include " "` conding convention come from? (#15522)

Kaspar Schleiser notifications at github.com
Mon Nov 30 12:40:18 CET 2020

> Where does the `#include` coding convention come from?

Style. `"foo.h"` is "one of ours", whereas `<foo.h>` is "comes from the runtime/libc/whatever". That only goes upstream, we consider package headers as "ours".
The angle brackets form searches "preconfigured list of standard system directories". For RIOT being a library OS usually compiled to a baremetal target, that means toolchain provided include paths. Quote includes search paths added with `-I` __before those__. So using the quote form __hints to the reader__ that "we don't expect this to be found in the toolchain include paths".

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...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201130/41697f35/attachment.htm>

More information about the notifications mailing list