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.
I can agree with this statement of fact. I'm missing the part where it's relevant to the conversation or informs some conclusion.
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.
> 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.
I guess instead we must embed GUIDs in every file to keep track of uniqueness.
[0]: https://stackoverflow.com/a/13172784/218830
[1]: https://stackoverflow.com/a/1866547/218830