[riot-notifications] [RIOT-OS/RIOT] build system: add machine-readable RIOT_VERSION_CODE macro (#16765)

chrysn notifications at github.com
Tue Sep 21 17:27:58 CEST 2021

Summarizing some chat exchange, I still think that rather than having anyone rely on particular versions we should rather expose features declared in, say, `<apifeatures.h>`, that indicate that a particular change was enacted. Unlike versions, this would naturally work with any number of branches, releases or merges, for as long as these names (eg. `#define RIOT_APIFEATURE_CPUINIT_CALLED_FROM_STARTUP`) are unique. They'd be kept indefinitely (but might after many releases be marked for deprecation in order to hint to users that unless they use *really* old versions they can just as well assume the feature to be present).

Sadly I don't have the time right now to follow this through completely, but I still suggest that it be held as an available option for cases in which version number checking reaches its limitations.

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/20210921/dc2dbc31/attachment.htm>

More information about the notifications mailing list