[wwwdocs] Update coding conventions for C++

Gabriel Dos Reis gdr@integrable-solutions.net
Sun Jul 1 14:43:00 GMT 2012


On Fri, Jun 29, 2012 at 1:17 PM, Lawrence Crowl <crowl@google.com> wrote:
> Resend, as I replied to a message that didn't have the usual suspects
> on the cc line.
>
> On 6/27/12, Lawrence Crowl <crowl@google.com> wrote:
>> ..., does anyone object to removing the permission to use C++
>> streams?
>
> Having heard no objection, I removed the permission.

This is an area where I think we should not be too
prescriptive.  Clearly, the diagnostics machinery will be used
for anything diagnostics -- so whether IOStreams are
allowed or not would not change that.  On the other hand, I feel
we should defer to maintainers' discretion in specific areas
whether people are implementing dumping or other I/O facilities
not related to diagnostics, since as I you correctly pointed out,
there is an added value of flexiibility and expressivity.

In summary: Instead of blanket ban, I would suggest that uses
for C++ I/O streams be reserved for non-diagnostics purposes
 and left at the discretion of maintainers.

>
> The following patch is the current state of the changes.  Since the
> discussion appears to have died down, can I commit this patch?



More information about the Gcc-patches mailing list