Cool. Thanks Johny. learn something everyday.
I went and stared at section 11 to see what Johny was talking about and you
should be able to use the '@C' attribute notation.
eric
2012/1/10 Johny Mattsson
> Hello Anna,
>
> You can use nesC annotations to prevent the name mangling. Have a loo
Hello Anna,
You can use nesC annotations to prevent the name mangling. Have a look at
section 11 in the nesC 1.3 language reference manual. The first two are the
ones which apply to your situation. Depending on the exact use case you may
or may not need the second one. If you don't need it, then E
Hi,
I am Yuanwen Ji. I am recently doing* Crossbow MTS400 IRIS *sensor node
connection in my lab.
I followed instruction how to set up the node. However MoteView always show:
[MV] unkown packet: 0x0077...
Moreover, in the node list, I can only see the base node,
Only definitions that are inside an implementation block actually have name
mangling occur.
So if you pull the function outside (or the forward reference definition
outside) then it won't be mangled and it should then work as you desire.
But do follow Michael's advise, you should be able to do re
Search this list and the doc site http://docs.tinyos.net/
for advice on calling C functions and libraries from TOS.
That's the opposite of what you want, but you may find
something in the various described approaches for getting
around the name mangling.
MS
Anna Förster wrote:
> Hi all,
>
> I am
Hi all,
I am trying to implement a tinyos interface to a software library. The problem
I am currently facing is that the NesC compiler re-names all functions like
this:
in BlinkC.nc I define for example MY_FUNCTION
And then it is converted to BLINKC_MY_FUNCTION
Well, what I am actually trying
