Hi Ludwig,
In my simple tinking the macro approach does not exclude the API, just a
pseudo code example:
API log_api.h:
...
void log.info(const char* fmt, ...);
...
#ifdef ENABLE_INFO
#define LOG_INFO(...) log.info(__VA_ARGS__)
#else
#define LOG_INFO(...)
#endif
In RIOT framework and
Hi Joakim,
+1 from my side!
Cheers,
Hauke
On 23.02.2015 09:35, Oleg Hahm wrote:
Hi Joakim!
I'm completely fine with that. Thanks for the effort!
Cheers,
Oleg
Am Mon, Feb 23, 2015 at 09:18:42AM +0100 schrieb Joakim Gebart:
I'd like to hear if anyone is strongly opposed to this, otherwise I
Hi Attilio,
personally I think Macros might not be the best idea - one of the design
principles of RIOT so far is to limit the use of Macros to the minimum.
You can actually get the same results for the code below by using a
plain API based approach:
log_api.h:
void log_info(...);
Dear rocking IoTlers,
due to the embedded world this week, several maintainers won't be available
for this week's PlaceCam meeting. Hence, I have two questions:
1.) Is there anything urgent to discuss or can we skip the meeting?
2.) If we don't want to skip the meeting, is there anyone available
Hi Joakim!
I'm completely fine with that. Thanks for the effort!
Cheers,
Oleg
Am Mon, Feb 23, 2015 at 09:18:42AM +0100 schrieb Joakim Gebart:
I'd like to hear if anyone is strongly opposed to this, otherwise I
will go ahead and create a new repository tomorrow.
Best regards,
Joakim Gebart
Hi Joakim!
What is a suitable name for the new repo?
I have been using riotbuild for my Docker development at
https://github.com/gebart/riotbuild
I don't have any particular ideas for the name, so, for me riotbuild (or
riotdocker) would be fine.
Also, I need to have an organisation owner
