pcp
[Top] [All Lists]

Re: [pcp] RFC pcp update: pmParseUnitsStr() function

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] RFC pcp update: pmParseUnitsStr() function
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 15 Dec 2014 16:48:28 -0500 (EST)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20141215161606.GH14953@xxxxxxxxxx>
References: <20141201154517.GK5088@xxxxxxxxxx> <548B491B.1030705@xxxxxxxxxx> <20141212212048.GE14953@xxxxxxxxxx> <548F0109.1060103@xxxxxxxxxx> <20141215161606.GH14953@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: 25Kfe5xyBMFGT4lxnBW9HzuisWslaA==
Thread-topic: RFC pcp update: pmParseUnitsStr() function

----- Original Message -----
> Hi -
> 
> > >Evidently yes, they're all over the code base.
> 
> > Sorry, I should have been more direct with that comment. As a matter of
> > style, we should have these kinds of comments only in C++ code.
> 
> OK, but
> 
>    % git grep "//" -- "*.c"
> 
> over the source tree shows many C files with this C99-compliant notation.

FWIW, I agree with Dave - always follow the style of the code being changed.
e.g. libpcp is all C-style comments (barring one silly TODO comment :) - heh
and thats in interp.c so noones game to touch it I guess!)

> > Can you please convert the ones in this code?
> 
> Changed.
> 
> > As we notice other instances, we should fix them as well.
> 
> Would you like a patch for the other 1200+ instances in the code base?

Just use the style that matches the code being modified (the other places
are isolated - like specific C PMDAs where the author chose to prefer //
style comments - and that's fine, we follow that style if modifying that
code).

thanks.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>