Hacker News Reader

Comment by saagarjha | Hacker News Reader

I’ve done

  gcc foo.c -o foo.c

far too many times :(

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.