Nevermind,
I am exploring using function pointers; it compiles, I guess as they
aren't used in command/event signatures.
Also discovered the C attribute - I am hoping this will allow access to
the modules namespace. If anyone is curious, read the 'nesC 1.1 Language
Reference Manual', in
Also realised that
keywords like static or extern, do sod all as I discovered when
my app wouldn't compile due to redefinition errors.
Just wanted to share this in-case anyone else had special needs that
necessitated coding against the nesC/TinyOS programming model.
Darren
Darren BISHOP
On Aug 18, 2006, at 1:55 AM, Darren BISHOP wrote:
Hi All,
Ted: Can you give details on your debugging interface?
Phil: I have implemented a C function with declaration 'extern
result_t lprintf(result_t *status, char *format, ...). The
definition is included by a LoggingM component that
Darren,In reference to calling nesC commands from a C function, I recently posted a similar question and got an answer. Here's a link to the thread:
http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-July/017770.htmlCheers.-jayOn 8/18/06, Philip Levis
[EMAIL PROTECTED] wrote:On Aug
Today was a day of discovery.
I am using tinyos-1.x and thus nesC1. I found the C attribute after reading
the reference manual and in doing so got a concrete understanding of how nesC
works on the whole.
The way I have implemented my logging API, it no longer matters who uses the
UART and
