This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [wwwdocs] Update coding conventions for C++


On 7/1/12, Gabriel Dos Reis <gdr@integrable-solutions.net> wrote:
> 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 flexibility 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.

Given that maintainers have discretion to grant exceptions
anyway, would you be willing to let the wording stand without
that permission?

I'd like to get the document committed in some form so that we can
make progress on the dependent activities.  At present, none of
those activities depend on this issue.

-- 
Lawrence Crowl


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]