3 ms·
If there's a valid need for the distinction, and it's straightforward (<>s search system libs first vs quotes search CWD first IIRC), what would be less ugly? K
by krisrm 7y ago
If there's a valid need for the distinction, and it's straightforward (<>s search system libs first vs quotes search CWD first IIRC), what would be less ugly? Keeping in mind the vast number of C++ files out there that have already baked this convention in :)
- Razengan 7y agoHow about using the CLI path resolving convention, where you implicitly look in the CWD first and then the environment path? Specify specific paths by something like "$SYSTEM\foo.h" or "$CWD\foo.h" Either would be more readable and less magic than <> or ""