From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id 925B83858017 for ; Fri, 7 Jan 2022 18:34:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 925B83858017 Received: from linux-libre.fsfla.org ([209.51.188.54]:59358 helo=free.home) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n5u4F-00037D-95; Fri, 07 Jan 2022 13:34:23 -0500 Received: from livre (livre.home [172.31.160.2]) by free.home (8.15.2/8.15.2) with ESMTPS id 207IXsKh654943 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 7 Jan 2022 15:34:12 -0300 From: Alexandre Oliva To: Martin Jambor Cc: GCC Mailing List Subject: Re: Mass rename of C++ .c files to .cc suffix? Organization: Free thinker, not speaking for the GNU Project References: Errors-To: aoliva@lxoliva.fsfla.org Date: Fri, 07 Jan 2022 15:33:54 -0300 In-Reply-To: (Martin Jambor's message of "Fri, 07 Jan 2022 11:25:50 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.84 X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2022 18:34:27 -0000 On Jan 7, 2022, Martin Jambor wrote: > Would anyone be terribly against mass renaming all *.c files (that are > actually C++ files) within the gcc subdirectory to ones with .cc suffix? I wouldn't mind that. > (Any important caveats I might have missed?) Having recently renamed a .c source to .cc in a development branch, one annoying issue that came up was that dependency tracking in build trees couldn't recover from the renaming on its own: it kept on insisting that the previously-existing .c file was missing, instead of picking up the .cc. This could be a problem for hands-off CI testers, besides the slight annoyance of having to wipe out the build tree, or at least hunt down and remove dep-tracking files. It's no biggie, I'm not sure there's some change to the build machinery we could make ahead of time to alleviate this, but it should probably be mentioned in the announcement of the change if/when it goes in. -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Disinformation flourishes because many people care deeply about injustice but very few check the facts. Ask me about