Hi Brad: On Tue, Jun 3, 2008 at 7:51 AM, Brad Nicholes <[EMAIL PROTECTED]> wrote:
> Without really looking at this issue in detail, I wonder if it would be > better to create an include/gexec.h file and move the gexec related structs > there rather than put them in ganglia.h. My guess is that most consumers of > ganglia.h will not need any of the gexec structs. If the gexec structs are > in their own header, then those that need gexec can just include the header > specifically. It also looks like the gexec structs are only referenced in > lib by ganglia.c (which I think is mis-named. The original name looks like it > was gexec_funcs.c). This one .c file could include gexec.h and the rest of > lib could remain as is. Does this make sense? This is a good idea, I'll see what I can come up with. Thanks, Bernard ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
