Timeline for The case against path expressions in #include directives
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2024 at 10:49 | history | edited | Vroomfondel | CC BY-SA 4.0 | Additional foreign discussion material |
| Nov 22, 2021 at 17:56 | history | edited | Vroomfondel | CC BY-SA 4.0 | added 36 characters in body |
| Apr 7, 2020 at 8:21 | history | edited | Vroomfondel | CC BY-SA 4.0 | added 1228 characters in body |
| Apr 2, 2020 at 18:00 | history | tweeted | twitter.com/StackSoftEng/status/1245773179722874881 | ||
| Apr 1, 2020 at 15:21 | comment | added | Robert Harvey | Your opinion, and that of your team, is the only one that really matters. This isn't an Automotive Configuration Management problem; it is a problem of ordinary C conventions that are universally applicable to all problem domains. Conventions are only useful if you and your team can follow them. | |
| Apr 1, 2020 at 10:23 | comment | added | Vroomfondel | @RobertHarvey I regret pushing the discussion in the <> or "" direction. The uncontrollability of include mishaps is more of a concern to me. What is the opinion of other ppl tasked with Automotive configuration management? | |
| Mar 27, 2020 at 20:06 | answer | added | besc | timeline score: 9 | |
| Mar 27, 2020 at 19:26 | comment | added | Robert Harvey | Well, I'm totally on board with your POV. The problem is that time is finite, and if this is a large project it might not be worth the time to make the necessary changes. | |
| Mar 27, 2020 at 19:11 | comment | added | user4828 | Hmm. I guess I focus on the first sentence in the paragraph: "This variant is used for system header files". I acknowledged that it's not formally reserved, but I've always found it useful to have a notation that distinguishes system and standard library headers from project level headers. Since it shows up in so many coding standards I suspect a lot other folks find it useful too. | |
| Mar 27, 2020 at 19:04 | comment | added | Robert Harvey | Check out the Gnu documentation: "#include <file> -- This variant is used for system header files. It searches for a file named file in a standard list of system directories. You can prepend directories to this list with the -I option." | |
| Mar 27, 2020 at 19:02 | comment | added | Robert Harvey | A style guide suggestion is not the same as "reserved for system headers." | |
| Mar 27, 2020 at 19:00 | comment | added | user4828 | @πάνταῥεῖ you are correct that <> is not formally reserved in the language spec, but it's discouraged to use them for project level includes in every coding standard I've worked with. See for example Google C++ style guide | |
| Mar 27, 2020 at 18:59 | comment | added | πάντα ῥεῖ | There's no particular correct way. Best let your build system handle that. But saying that the <> syntax is reserved for platform headers is plain wrong. Regarding my nick, that's intentional of course :-P. | |
| Mar 27, 2020 at 18:52 | comment | added | Vroomfondel | @πάντα ῥεῖ So which is the correct take on this then? BTW your user handle is particularly nasty to reply to from a mobile device #justsaying | |
| Mar 27, 2020 at 18:30 | review | Close votes | |||
| Apr 1, 2020 at 3:05 | |||||
| Mar 27, 2020 at 18:11 | comment | added | πάντα ῥεῖ | "AFAIK <> is reserved for system headers coming from the platform, and are strongly discouraged to be used by project code." That assumption is wrong. | |
| Mar 27, 2020 at 18:08 | history | asked | Vroomfondel | CC BY-SA 4.0 |