[Ns-developers] module headers for example scripts
Gustavo Carneiro
gjcarneiro at gmail.com
Wed Mar 26 11:22:16 PDT 2008
On 26/03/2008, Mathieu Lacage <mathieu.lacage at sophia.inria.fr> wrote:
>
>
> On Wed, 2008-03-26 at 16:36 +0000, Tom Henderson wrote:
>
> > 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.
>
>
> +1 to explicit enumeration.
OK, since everyone seems to agree. Done.
>
> > 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.
>
>
> +1 to packetsink-module.h although it is quite unlikely you will ever
> need to include it if you include helper-module.h which includes
> packet-sink-helper.h for you.
I guess nothing needs to be done here.
regards,
>
> Mathieu
>
>
--
Gustavo J. A. M. Carneiro
INESC Porto, Telecommunications and Multimedia Unit
"The universe is always one step beyond logic." -- Frank Herbert
More information about the Ns-developers
mailing list