[Tinyos-devel] Re: [Tinyos Core WG] Proposal for
VariableSizedQueueC component
Kevin Klues
klueska at gmail.com
Tue Sep 18 22:05:02 PDT 2007
> How about calling it QueueP.nc? Also, would this also make sense with
> PoolP?
The problem is that we also need to redefine the Queue interface to
contain a new parameter, not just tack it onto a new QueueP component.
We need Queue to look like this now:
interface Queue<t, queue_size_t> {
command queue_size_t size();
command queue_size_t maxSize();
command t element(queue_size_t idx);
....
}
So the question is whether we want to leave QueueC backwards
compatible with the way it was or not. To do so requires something
like I described before that involves both a component similar to the
VariableSizedQueue component I described as well as a QueueP component
that does the proper mapping from a VariableSizedQueue interface with
uint8_t passed as the queue_size_t parameter to the original Queue
interface. I personally think the original Queue interface looks
nicer without this extra parameter, but it's necessary if we want
queue sizes that aren't fixed.
Oh.... and for pools it does make sense to do something similar once
we reach an agreement...
--
~Kevin
More information about the Tinyos-devel
mailing list