In the next few days, the tinyos-1.x tree is going to transition to nesC
1.1. This transition will be specification of whether interfaces are
synchronous or asynchronous, and adding the necessary atomic sections to
components.
If you are using the nesc 1.1 compiler, you should have no problems.
Hopefully, your code will run with greater stability as we remove race
conditions. The 1.1 code should work with the 1.0 compiler, but we don't
guarantee it. Among other things, hand-written atomic sections have been
replaced with the atomic language primitive (which the 1.0 compiler
ignores), so new race conditions may appear.
Kristen Wright has put a tag on CVS, tos-1-1-0-pre1, to mark the sources
before this transition. If you are still using the 1.0 compiler, I
recommend that you use this tagged version of the source.
Phil
----------------------
Society can and does execute its own mandates: and if it issues wrong
mandates instead of right, or any mandates at all in things with which
it ought not to meddle, it practises a social tyranny more formidable
than many kinds of political oppression, since, though not usually
upheld by such extreme penalties, it leaves fewer means of escape,
penetrating much more deeply into the details of life, and enslaving
the soul itself.
- John Stuart Mill, "On Liberty"
On Fri, 23 May 2003, David Gay wrote:
> The 1.1 pre-release is now on a branch (tag: v1_1_pre). The main branch
> should be considered unstable (it is acquiring an implementation of
> instantiatable components). So if you're getting nesC from CVS, I would
> recommend switching to the branch next time you update
> (cvs update -r v1_1_pre).
>
> David Gay
> [EMAIL PROTECTED]
>
> _______________________________________________
> Tinyos-devel mailing list
> [EMAIL PROTECTED]
> http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-devel
>
_______________________________________________
Tinyos-users mailing list
[EMAIL PROTECTED]
http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
