Hello everybody,
I came across an example of using the '@safe()' function in declaring the nesC
configuration file, for example: module BlinkC '@safe() { }'
I knew that the normal declaration of the configuration file is just: 'module
BlinkC { }' --> without the @safe() function.
When I compile the codes, nesC compiler produces a same output with a same
amount of compiling bytes. I cannot see the differences...
Can someone tell me what is the purpose of the @safe() function?
Thanks in advance.
Yusnaidi
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
