Markus Elfring

Search patterns can be specified for questionable source code places. They can become more sophisticated on demand, can't they? :thinking:

How do you think about to distinguish the storage location for provided files between the current source folder and a known installation directory for this software library?

:thought_balloon: I suggest to avoid that such software components [depend on undefined behaviour](https://www.securecoding.cert.org/confluence/display/c/CC.+Undefined+Behavior#CC.UndefinedBehavior-ub_106 "Avoiding undefined behaviour?").

:thought_balloon: Would you like to distinguish remaining open issues better for the involved software libraries?

:thought_balloon: How will the chances evolve to [delete misplaced underscores from affected identifiers](https://en.cppreference.com/w/cpp/language/identifiers#In_declarations "Description for reserved identifiers")?

I suggest to reconsider the consequences of [the following wording](http://c0x.coding-guidelines.com/6.10.2.html) from [the section "16.2 Source file inclusion"](http://open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3797.pdf) in the standard specification for the programming language "C++". ``` … The named...

There are different opinions about the handling of the involved implementation-defined behaviour. - Will header files be also searched outside the specified include directories if double quotes are used for...

Can you imagine use cases where you would like to exclude the search in "local" directories?

Yes. - This is the reason for my feature request here. How much do you care where the include files are safely stored for a software library?

I find it important to be reasonably sure that the desired computations were really correct because it could be determined by the applied software build parameters that the used functions...