News for hackers. Stuff that matters.
Re:Google C++ Style Guide Is No Good by bluGill on Thursday November 29, 2018 @11:24AM (#18561366)
clang actually does have the warning you want gcc to have - this is how I found our instances of it.

What none of the above can do is two different projects have MESSAGE_H headers that are different can fully compatible to include both. #pragma once handles this correctly.

Re:Google C++ Style Guide Is No Good by kazinator on Thursday November 29, 2018 @01:00PM (#18562211)
The clash between two different MESSAGE_H can be rendered vanishingly unlikely by having a convention of adding some random digits.

I adopted the following pattern some twenty years ago of affixing a random 32 bit number in hex:

   #ifndef MESSAGE_H_3DF0_9A73
   #define MESSAGE_H_3DF0_9A73

   #endif
Re:Google C++ Style Guide Is No Good by loeg on Thursday November 29, 2018 @09:54PM (#18566243)
If only the filesystem would assign some sort of unique, 32- to 64-bit identifier to files that a compiler could use to distinguish one header from another. We could call them inode numbers. Hmm. No, I'm sure no one has ever thought of the problem of identifying unique files before.[0][1]

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

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.