[Ns-developers] module headers for example scripts
Tom Henderson
tomh at tomh.org
Wed Mar 26 09:36:17 PDT 2008
Gustavo has modified waf to generate headers that can be used in example scripts, to avoid having to enumerate all of the lower-level header files. Presently, the following are generated:
./core-module.h
./packet-sink-module.h
./common-module.h
./point-to-point-module.h
./global-routing-module.h
./udp-echo-module.h
./mobility-module.h
./internet-node-module.h
./csma-module.h
./helper-module.h
./simulator-module.h
./onoff-module.h
./olsr-module.h
./node-module.h
./wifi-module.h
./contrib-module.h
where, e.g., simulator-module.h includes all of the public headers for /src/simulator.
I have two questions about the details:
1) should these module headers be cumulative or not? For instance, internet-node-module.h includes already simulator-module.h, node-module.h, etc.-- all of the build dependencies. I would slightly favor enumerating them (not aggregating across module boundaries), just for clarity sake, but that would mean more include statements-- all scripts would include "simulator-module.h" and "core-module.h" explicitly, for instance.
2) is the above the right granularity? An alternative would be to aggregate at the "module" level, which is one level below src/, which would mean having an "application-module.h" instead of a "packetsink-module.h", a "device-module.h" instead of "wifi-module.h", etc.
Other thoughts?
Tom
More information about the Ns-developers
mailing list