Hello Oleg,
that would be even better indeed.
something like #define LOG_PRINTF(...) LOG(LOG_PRINTF, __VA_ARGS__) and to
forbid to use printf?
wbr
malo
On 1 March 2016 at 20:31, Oleg Hahm <oliver.h...@inria.fr> wrote:
> Hey malo!
>
> On Tue, Mar 01, 2016 at 08:25:23PM +0100, malo wrote:
> > what about to have at least "official" wrapper around printf?
> >
> > Im using tinyprintf already with riot and to have PRINTF macro defined
> > would make things much easier.
> > There are DEBUGs and LOGs together with printf-s sprinkled in the code.
> > While DEBUG and LOG can be defined to custom functions, printf no.
> Thinking
> > at printf.h with PRINTF macro + formatter macros defined - bad idea?
>
> I would rather do the other way around and get rid of all the printfs in
> RIOT
> and replace them by DEBUG and LOG_*.
>
> Cheers,
> Oleg
> --
> printk("WE HAVE A BUG HERE!!! stk=0x%p\n", stk);
> linux-2.6.6/drivers/block/cciss_scsi.c
>
> _______________________________________________
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
