5 ms·

why not just do gcc main.c && ./a.out

• smabie 6y ago
  That doesn't include the headers. It also leaves a.out on your system.
  • sigjuice 6y ago
    What are the headers in this context that are not getting included? Shouldn't main.c include any necessary headers?
    • smabie 6y ago
      Yes, but runc includes the headers for you.
      • sigjuice 6y ago
        I'm sorry, I don't see the benefit of runc including a small list of headers for me. A small test program like main.c ought to be self-contained and might need headers not supplied by runc.
  • glouwbug 6y ago
    I mean, take it one step further then: gcc main.c && ./a.out && rm -f a.out
    • sigjuice 6y ago
      What is the big deal with just leaving the a.out alone? I might need to run it again, maybe with different arguments. A few a.out files from test programs are not exactly worth fussing over IMHO.
      • glouwbug 6y ago
        To each their own. If you're in vim, you don't need to leave your editor if you prepend an exclamation mark to the above expression. I often do a lot of prototyping with: !gcc main.c -fsanitize=address -Og && ./a.out