C for high level programmers (slides)

Re:C for high level programmers (slides) by NhanH on Sunday May 31, 2015 @10:14PM (#9636471)

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.

[ Parent | on HN ]

Re:C for high level programmers (slides) by pjc50 on Monday June 01, 2015 @05:27AM (#9637482)

I 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.

[ Parent | on HN ]

Re:C for high level programmers (slides) by fao_ on Monday June 01, 2015 @02:11PM (#9640841)

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.

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.

[ Parent | on HN ]