Hey Malo! On Wed, Mar 02, 2016 at 08:51:51AM +0100, malo wrote: > that would be even better indeed. > something like #define LOG_PRINTF(...) LOG(LOG_PRINTF, __VA_ARGS__) and to > forbid to use printf?
Hm, after thinking about this again, it's a bit more difficult, I guess. There are three types of actions where I see a need for printing strings: 1.) logging (something similar to syslog or journal on Linux) 2.) debugging 3.) some kind of CLI (e.g. our shell) 1.) should be covered by LOG_* from log.h. 2.) is covered by DEBUG() 3.) still needs a concept But in general, I agree that getting rid of printf() all over the code is desirable. Cheers, Oleg -- The problem with a SQL security joke is that Sony don't get it.
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list [email protected] https://lists.riot-os.org/mailman/listinfo/devel
