From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2541 invoked by alias); 23 Sep 2016 19:36:18 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 2525 invoked by uid 89); 23 Sep 2016 19:36:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=justify, challenge X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 23 Sep 2016 19:36:15 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EFA2E116FBB; Fri, 23 Sep 2016 15:36:13 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id GrERG0LEXHzL; Fri, 23 Sep 2016 15:36:13 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id BAFDC116908; Fri, 23 Sep 2016 15:36:13 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id 2EDC242320; Fri, 23 Sep 2016 12:36:12 -0700 (PDT) Date: Fri, 23 Sep 2016 19:53:00 -0000 From: Joel Brobecker To: Yao Qi Cc: Pedro Alves , "gdb-patches@sourceware.org" Subject: Re: [PATCH] gdb: Replace operator new / operator new[] Message-ID: <20160923193612.GG3842@adacore.com> References: <1474543227-19614-1-git-send-email-palves@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2016-09/txt/msg00315.txt.bz2 > To be clear, I didn't suggest renaming all .c files to .cc files. In case > that we add a new file, I wonder we may name it .cc. > > If mixed .c and .cc is confusing, I am fine with cpp files with .c suffix. I think it's best to stay with .c for practical reasons. Otherwise, the massive rename is going to create one "interesting" challenge for everyone who's maintaining a set a patches they haven't/couldn't contribute... Since the benefit is fairly minimal, it doesn't seem to justify the cost, IMO. -- Joel