3 ms·
Interestingly, I first started with C (although I haven't written a line of C code for a long time), and when I first move to higher-level languages, I dislike
by NhanH 11y ago
Interestingly, I first started with C (although I haven't written a line of C code for a long time), and when I first move to higher-level languages, I dislike the fact that I have no idea where the file I just imported is. Moreso when I'm playing with obscure/ new language: if I can just import whatever files I wanted (rather than at package level), it seems that would be much easier to hack on the language/std itself.
- pjc50 11y agoI have no idea where the file I just imported is A sufficiently long include path can give you this problem anyway. I recently tripped over this when I created a "reason.h" and discovered that Windows had a file of the same name deep inside MFC.
- fao_ 11y agoI recently tripped over this when I created a "reason.h" and discovered that Windows had a file of the same name deep inside MFC. It is my understanding that that would be solved by placing your file in a local directory called 'inc/' and having: #include "inc/reason.h" instead of: #include <reason.h> (or just replacing "" with <>). But I have never programmed in VSC before, so I may be wrong.