Re: Namespacing of Zephyr headers and API
On Mon, 3 Apr 2017 11:37:18 +0200
Tomasz Bursztyka <email@example.com> wrote:
Hi Paul,Yes, sure, that's what I meant too, a directory prefix, not a filenameHello,It could be solved by having 'include/zephyr' as a directory where to
prefix, sorry if it sounded like that.
Yes, like each and every Zephyr function to start with a common string2. About the same is true for Zephyr API calls either. At leastWhat do you mean as a whole? Like same unique prefix for all
prefix. But as I mentioned, I couldn't think of a perfect prefix
myself. E.g. "zephyr_" is too long, "z_" is perhaps too short and
unclear (I wonder what ZFS uses as a prefix for example). "zep_" might
be the right length, but maybe not the best abbreviation (well, we use
it in Jira, but that's Jira ;-) ).
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog