Hi Attilio, Martine, are you suggesting macros are better than APIs + functions? If so, please explain why and what better means ;)
Cheers, Ludwig On Mon, Feb 23, 2015 at 09:26:34AM +0100, Attilio Dona wrote: > Also for me the MACRO approach has to be considered in a design review, > eventually in addition to a tracing API layer. > > Just to add my bit of experience with RIOT about porting msp430 family on > new TI/redhat gcc 4.9: > > the default nanolib bundled with the toolchain implies a big printf memory > usage, not suitable for a lot of msp430 chips. > > At the moment my solution is to use tinyprintf: > > https://github.com/cjlano/tinyprintf > > It works as expected, with some minor modification to suit my port. > > Greetings > Attilio > > > > > > > > > On Mon, Feb 23, 2015 at 8:24 AM, Martine Lenders <authmille...@gmail.com> > wrote: > > > +1 thought about this for a long time, too. Though my approach would be > > with macros and more global (similar to how DEBUG is now). > > > > Am 23.02.2015 07:16 schrieb "Ludwig Ortmann" <ludwig.ortm...@fu-berlin.de > > >: > > > > > > > > Hi Jozef, > > > > > > AFAIK there has been no work on a solution so far. > > > However, I thought about this the other day in the context of the > > function pointer discussion and would like to propose a "logging" API > > (maybe there is an issue for that as well somewhere) for `core`, which > > offers things like `log.info(...)` and `log.error(...)`. > > > Different logging modules can implement this API then, ranging from > > `printf` over file based logging to network messages. > > > And then there should also be a `(void) ...` implementation which suits > > production and ultra low memory needs. > > > > > > Opinions? > > > > > > Cheers, Ludwig > > > > > > Am 23. Februar 2015 03:16:33 MEZ, schrieb Jozef Maslik < > > ma...@binarylemon.com>: > > > > > > > >Hi, > > > > > > > >Could you please give me information about actual state of "replace > > > >printf and puts" issues? https://github.com/RIOT-OS/RIOT/issues/994, > > > >https://github.com/RIOT-OS/RIOT/issues/641 > > > > > > > >I’m working with MKL02Z32 which has 4kB RAM. Printf or puts which are > > > >almost everywhere make a big problem. I removed them from my fork, but > > > >it is not good or nice solution. > > > > > > > >If I miss something important around “printing issue” please correct > > > >me. > > > >How others deal with this issue? (printf or puts usage like here, is > > > >not nessesary in real applications). > > > > > > > >Regards, > > > >Jozef > > > > > > > >_______________________________________________ > > > >devel mailing list > > > >devel@riot-os.org > > > >http://lists.riot-os.org/mailman/listinfo/devel > > > > > > _______________________________________________ > > > devel mailing list > > > devel@riot-os.org > > > http://lists.riot-os.org/mailman/listinfo/devel > > > > > > _______________________________________________ > > devel mailing list > > devel@riot-os.org > > http://lists.riot-os.org/mailman/listinfo/devel > > > > > _______________________________________________ > devel mailing list > devel@riot-os.org > http://lists.riot-os.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
