From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 128777 invoked by alias); 10 Dec 2019 22:19:39 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 128768 invoked by uid 89); 10 Dec 2019 22:19:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-17.4 required=5.0 tests=AWL,BAYES_00,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy=H*r:sk:gdb@sou, peoples, HX-Received:f1d4 X-HELO: mail-oi1-f170.google.com Received: from mail-oi1-f170.google.com (HELO mail-oi1-f170.google.com) (209.85.167.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Dec 2019 22:19:38 +0000 Received: by mail-oi1-f170.google.com with SMTP id j22so11372101oij.9 for ; Tue, 10 Dec 2019 14:19:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=mhmc5m6wKB4KbeB09SwMbKQX4cCwVG2pYm+RTiJUCBc=; b=PDmLMh28solze6sbplATtxd4ZjJlvpqeW+x/DgkZSdHFfpIzz+Qo2Hv2R3ntecI4wR 1/E4KJM2RTsBRzmdPR9nOVVfG1yrfq/q50cMiznDV6pfPrc984+HD2Ps9l+SbF6aoQEk DNCVzkLzo5hRDNDXGyhUFGv83HHnwWO+VBbNpKQHsNO50NqXmcFuVRn8ZfZ6nDfaytQ7 Pr5oR6uSRZbWxE80P5GibJz305Az0LXbH2Sf1M/sb/sB+touN72FM0nGunMa0rpiHgdc QXIWcYi2YbuEEmYcV294scbYyyP4sQRgwmUgXtl6LppwL1PUtJH+6zO0h+nd0Dnb7v5O 6+EA== MIME-Version: 1.0 From: "Christian Biesinger via gdb" Reply-To: Christian Biesinger Date: Tue, 10 Dec 2019 22:19:00 -0000 Message-ID: Subject: Renaming .c files to .cc? To: gdb@sourceware.org, Pedro Alves Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00001.txt.bz2 Hello all, I was wondering what people's thoughts are on renaming the .c files to .cc, since they are in fact C++ code? (Only for files under gdb/) Advantages: - Easier for newcomers to see that the code is, in fact, C++ - Editors will syntax highlight C++ keywords w/o having to be told that these files are C++ On IRC it was mentioned that git may have issues with renames like that but I have found that "git log --follow" and such are doing a good job with that, at least as long as the same commit doesn't change the file too much while it is renamed, which I wouldn't expect to be a problem here. Thoughts? Christian