News for hackers. Stuff that matters.
Re:Google C++ Style Guide Is No Good by kazinator on Saturday December 01, 2018 @05:54PM (#18579504)
Copies of a file have different inode numbers.
Re:Google C++ Style Guide Is No Good by loeg on Sunday December 02, 2018 @01:26AM (#18581109)
I can agree with this statement of fact. I'm missing the part where it's relevant to the conversation or informs some conclusion.
Re:Google C++ Style Guide Is No Good by kazinator on Sunday December 02, 2018 @02:14AM (#18581232)
It's relevant if I have a requirement that if a file happens to be duplicated, then the once-include mechanism should treat those copies as one object.

This could arise if the code is originally on a system where some header files are symlinks to a common file. These symlinks happen to break (due to the way the code is archived, or on some system that doesn't have symlinks or whatever); they turn into separate copies.

Exclusion that is keyed to a symbol that is encoded in the file has no problem with this; filesystem-id-based excusion doesn't handle the case.

Re:Google C++ Style Guide Is No Good by loeg on Sunday December 02, 2018 @08:31PM (#18585739)
> It's relevant if I have a requirement that if a file happens to be duplicated, then the once-include mechanism should treat those copies as one object.

I don't believe that is a reasonable requirement.