Philip Levis wrote:
On Oct 2, 2007, at 2:01 PM, David Gay wrote:
They are presumably a left-over from when we required all things
ending in C to be configurations.
Proposal: get rid of these configurations, i.e., rename the *P
module to *C.
I'll do this next week if I hear no screams...
I think it was that way for the random number generators because the
C's at one point did the autowiring to SoftwareInit. That has since
moved into RandomC. To be honest, it should be in the C's, so that
you can use them without wiring to SoftwareInit.
So do the following changes:
RandomC is just a selection of RandomMlcgC
RandomLfsrC/RandomMlcgC do the Init auto-wiring
NoLedsP replaces NoLedsC
Sounds good to me. Yay code refactoring.
As I understand the naming convention, C's stand for common, and P's stand for
private,
and a configuration can stand alone, but a module needs a configuration.
Modules and configurations can be either P's or C's.
What else makes a concise rule set for naming?
Thanks,
John Griessen
--
Ecosensory Austin TX
tinyOS devel on: ubuntu Linux; tinyOS v2.0.2; telosb ecosens1
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
