Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Kaspar Schleiser
Hi, On 05/10/15 10:38, Oleg Hahm wrote: >>> I would claim that this is impossible. Even a simple puts() already affects >>> the timings, calls peripheral drivers, and may cause interrupts. >> "the same" was bad wording. I meant semantically, like Martine initially >> stated. > > I guess you mean

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Oleg Hahm
Hi Kaspar! > > I would claim that this is impossible. Even a simple puts() already affects > > the timings, calls peripheral drivers, and may cause interrupts. > "the same" was bad wording. I meant semantically, like Martine initially > stated. I guess you mean Ludwig. I just wanted to point out

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Kaspar Schleiser
Hi, On 05/10/15 09:34, Oleg Hahm wrote: DEVELHELP should not be used to change the semantics of things. >>> >>> Can you elaborate? >> The system should behave the same whether develhelp is used or not. > > I would claim that this is impossible. Even a simple puts() already affects > the timi

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Oleg Hahm
Hi! > >> DEVELHELP should not be used to change the semantics of things. > > > > Can you elaborate? > The system should behave the same whether develhelp is used or not. I would claim that this is impossible. Even a simple puts() already affects the timings, calls peripheral drivers, and may cau

Re: [riot-devel] LPM idle_thread

2015-05-10 Thread Kaspar Schleiser
Hi, On 05/09/15 20:24, Oleg Hahm wrote: >> DEVELHELP should not be used to change the semantics of things. > > Can you elaborate? The system should behave the same whether develhelp is used or not. If you do something like #ifdef DEVELHELP if(input_not_correct) { print("error message");