undefined | Better HN

0 pointssaagarjha6y ago0 comments

I’ve done

  gcc foo.c -o foo.c

far too many times :(

0 comments

3 comments · 2 top-level

loeg6y ago· 1 in thread

Seems like gcc should be smart enough to reject that mistake nowadays, right?!

I should write a shell frontend to gcc to warn if I do this…

I work in exactly two modes of `gcc` usage. I either accept `./a.out` as the name I deserve, or I write a `CMakeLists.txt`.

There nothing in between.

j / k navigate · click thread line to collapse