Thanks for your answer lads.
I've checked the whole system and there is no duplicate of the file EASAP.nc.
When I remove the definition in EASAP.nc interface, the compiler complains
(naturally):
interface has no command or event named `findNode'.
And there is no definition in EASAPImp
I got it...
I forgot a simple thing:
includes EASAP;
at the top of the interface declaration of EASAP.nc.
Which led to, as you said Michael, the compiler to 'help' with declaring the
function because 'struct node' is unknown for the interface...
Thanks lads.
Inderjit
Hi, I have a small problem compiling my module.
I have an interface (EASAP.nc):
interface EASAP
{
...
command struct Node* findNode(uint8_t id);
...
}
And in my module ( EASAPM.nc)
{
...
command struct Slot* EASAPImp.findSlot(uint8_t slot)
{
...
}
...
Could it be expecting EASAPImp.findNode(uint8_t id) rather than
EASAP.findNode(uint8_t
id) ?
-Brian
On 7/27/07, Inderjit Singh [EMAIL PROTECTED] wrote:
Hi, I have a small problem compiling my module.
I have an interface (EASAP.nc):
interface EASAP
{
...
command struct Node*
One possibility is that you are using findNode() in EASAPM
before the block that defines it. The compiler will help
you be making a default declaration with all int types,
and this will cause the real define to conflict with the
previous one...It's all part of the fun of making 'C' of
a stronger
