From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37970 invoked by alias); 11 Dec 2019 00:42:00 -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 37962 invoked by uid 89); 11 Dec 2019 00:41:59 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Received:1e13, H*i:sk:CAPTJ0X, tedious, H*r:192.168.15 X-HELO: mail-vk1-f193.google.com Received: from mail-vk1-f193.google.com (HELO mail-vk1-f193.google.com) (209.85.221.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 11 Dec 2019 00:41:58 +0000 Received: by mail-vk1-f193.google.com with SMTP id u6so6271988vkn.13 for ; Tue, 10 Dec 2019 16:41:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=pc8mc+Q0abS41jKfovI4gstzqX8MA75z2CotG4NZt9I=; b=FS6ZlzBMGHLMWNmSKWZupP3gbpr9lziL7orKjVlejCrXWLucBIXXkonz9nM9VDQGPU 4k0hr1T7Styfn5aXrfqCJ8NLMrYHcoirWbyB0nKz+jj6VsnGTco15e2qECIbQ/2HWyZY Y34TUTZyMuDdF8vqylRvofz/UytgOImDJfNhjejpQ+Co+wGezVl1a5nN5XBWUGqgAytC /T43W/dAX98Dj6A7HK0rcjIlm48C46/uJkLY/uJ7lAt4PEMYYcUsTyWmrr/0Ci/GlVeg 2hjqSjC+49hsswb9dD/OqqDkLEI56iPN+YAHQ5587825011ZtK54DuOIcRaDK001VceE eaYQ== Return-Path: Received: from [192.168.15.21] ([189.111.86.232]) by smtp.gmail.com with ESMTPSA id d8sm306564uan.13.2019.12.10.16.41.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Dec 2019 16:41:55 -0800 (PST) Subject: Re: Renaming .c files to .cc? To: Christian Biesinger , gdb@sourceware.org, Pedro Alves References: From: Luis Machado Message-ID: <1ae59e3e-9685-b9fa-49b5-71b29d709604@linaro.org> Date: Wed, 11 Dec 2019 00:42:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00002.txt.bz2 On 12/10/19 7:18 PM, Christian Biesinger via gdb wrote: > 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/) I don't have strong objections to this other than it may make things slightly more tedious to 'git blame' some files, as Tromey pointed out. But i think that is excusable compared to better organization of source files, for what they really are (C++ files). > > 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++ The above items sound like reasonable pluses. > > 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 >