On Wed, Jul 02, 2008 at 11:11:08AM -0600, Brad Nicholes wrote:
> >>> On 7/2/2008 at 5:12 AM, in message <[EMAIL PROTECTED]>, Carlo Marcelo
> Arenas Belon <[EMAIL PROTECTED]> wrote:
> > The following proposed patch for stable 3.1, removes all references to C++
> > as a supported language for building DSO metrics as it was reportedly not
> > working.
> > 
> > The changes required to get mod_example.c to compile using the GNU C++
> > compiler (which are rather intrusive) are already committed in trunk and
> > proposed for integration for the next release.
> > 
> > Contains changes from r1490.
> > 
> > Carlo
> > ---
> 
> Even though the language label of "C/C++" might be a little misleading for 
> now, it is still a more meaningful language label than "c".

I would argue otherwise, as "c" semantics will be more meaningful to an
"Objective C" or "C#" interface than "C/C++", and they all might be possible
in the long run.

Indeed I would even argue that "C/C++" is too limiting because any other
compiled language that is able to use "c" semantics might be represented here
as well.

> If we change to a language label of "c" now and then more fully support C++
later (which it looks like will happen in the next minor revision), we will
have to add another language label.

or just an alias to the current one, which is just 1 extra strcasecmp call.

> Internally there is no difference in how a C module or a C++ module would be 
> handled however to avoid confusion later, we would have to treat them 
> externally as being different.  I would suggest that we make the 
> documentation changes now but leave the "C/C++" language label alone.

the documentation changes reflect the change in the language tag to "c",
together with the explanation on how to use a C module, do you mean then to
keep the changes in the explanation but keeping all references to the language
tag even in the documentation as "C/C++"?

> I would rather keep the "C/C++" language label so that no configuration file 
> changes or code changes will be necessary in the next revision when C++ is 
> more fully supported.

are you arguing this patch doesn't get committed at all and we just release
this knowing C++ won't work and hoping to have it fixed before anyone finds
out the wrong way?

Carlo

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to