On Jan 7, 2022, Martin Jambor <mjam...@suse.cz> 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 <https://stallmansupport.org>
