On 11/9/06, Michael Schippling <[EMAIL PROTECTED]> wrote:
Philip Levis wrote: > On Nov 8, 2006, at 5:51 PM, Michael Schippling wrote: > >> It's not "duplication", it's overloading... >> I haven't done an exhaustive search, but each of >> the same-named files/modules has different behavior -- >> mostly due to platform or protocol differences. >> >> Care to re-invent C++ using directories instead of name-spaces? > > Except that the names are unique. It's just like changing the -I or -L > directives in C to include different header files or libraries. > Well yes...but they are secret -I and -L directives, which certainly took me by surprise and seems to be a constant source of confusion. For instance, I don't recall seeing anything in the general doc or tutorial that mentions that there is an implicit search order that includes all the mica derived platform directories. When one is trying to navigate the source without benefit of a tightly coupled IDE (which I still have not found...probably due to lack of trying...), it's akin to looking at good old 'C' without having ctags or grep... I probably already asked and was answered, but: Is the 'automagic' search order documented someplace obvious?
Well it's displayed every time you compile with -v... (along with the actual path used to load each component). Beyond that, it's also documented by "man ncc" (though that does have a placeholder for "whatever the platform chose to do"). There isn't currently any real per-platform documentation, though reading the .platform file isn't particularly hard (and see tutorial 10: http://www.tinyos.net/tinyos-2.x/doc/html/tutorial/lesson10.html ...). David Gay _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
