On Thursday 28 June 2007 11:06:31 pm Murtuza wrote: > Thts fine..but there is still one more thing to ask. > > If an event is not doing anything then why do we take the pains to include > it.. > > for example > in file tinyos-1.x/tos/platform/mica2/CC1000RadioIntM.nc there are some > "default events" which do nothing. They are not even implemented in some > other configuration. Then what purpose do they serve. ( I did not find an > explanation of this in the manual)
Note that the default events are implemented in the component that provides the interface. This means that components that come along later and use the interface implementation don't have to care about implementing event handlers as it normally must. This allows an interface provider implementation to effectively denote some events as optional from the perspective of the interface user. > > Thanking you once again > > MMA > > On 28/06/07, Brian Mulanda <[EMAIL PROTECTED]> wrote: > > When an event is preceded by "default", the compiler will not require you > > to wire this event when specifying your > > configuration. The nesC compiler will complain if an event, not preceded > > by default, is not wired within a > > configuration. > > > > You can read more about this in the nesC language reference manual here: > > > > http://nescc.sourceforge.net/papers/nesc-ref.pdf > > > > -Brian > > > > On 6/28/07, Murtuza <[EMAIL PROTECTED]> wrote: > > > hi friends, > > > > > > Can anyone tell me what a "default event" is? Why do we need the word > > > "default" in it...can we just say "event" ? > > > > > > Thanking You > > > MMA > > > > > > _______________________________________________ > > > Tinyos-help mailing list > > > [email protected] > > > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-he > > >lp > > !DSPAM:4685042779172032620075! _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
