Hmm... That makes sense.
But how can I know whether this is a split-phase or a blocking interface?
Because if I need something like this:
external int var;
event void Boot.booted(){
var = 10;
call MyInterface.DoSomething(var);
var = 20;
call MyInterface.DoSomething(var);
...
}
Actually after reading the in Timer interface, invoking
call Timer.startOneShot(55);
call Timer.startOneShot(66);
will cause only the second command to shoot:
The same will probably happen with my own interface.
Arik
On Fri, Feb 26, 2010 at 12:42, Arik Sapojnik sapoj...@gmail.com wrote:
I am probably wrong (and hopefully someone will correct me) but as far as I
understand it.I think all code continues to run in sequence across interfaces
until it ends. If a new task is posted it wont run until the current task has
completed .so in your example below DoSomething(10) will run
Thanks Mark,
So basically you think that interfaces are blocking.
Anyone can approve? :)
Arik
On Fri, Feb 26, 2010 at 14:42, Mark Proctor mp_markproc...@hotmail.comwrote:
I am probably wrong (and hopefully someone will correct me) but as far as I
understand it.
I think all code continues
I think it depends on the implementation. If there is any post in the
interface you are right and both DoSomething may use the same argument.
If there is no post each one will use their own.
Regards
Javier
El vie, 26-02-2010 a las 15:23 +0200, Arik Sapojnik escribió:
Thanks Mark,
So
Actually, if both of them use post, the second post can't be performed
(because you can't post the same task twice). So only one of them wil
execute.
Arik
2010/2/26 Javier Puiggros Vogel jpuigg...@wiseconn.cl
I think it depends on the implementation. If there is any post in the
interface you
Hi,
When I create a new interface which is provided by my new component - does
it automatically created as a split-phase interface?
If it is, what I actually want to figure out is can I call my interface
several times prior to the first completion?
Since I can't post the same task, it seems that
