6 ms·
Oh. Especially if one puts my script into ~/bin and calls '$ runc ..' I admit I didn't research the name 'runc'. Should I rename it ? I like this one because
by alcover 6y ago
Oh. Especially if one puts my script into ~/bin and calls '$ runc ..'
I admit I didn't research the name 'runc'.
Should I rename it ? I like this one because it's short and explicit.
- verdverm 6y agoyes, I would not consider using this given we use the more popular runc
- brudgers 6y ago"compileAndRunCSource" is explicit. People could #!bin/bash it however they want. I only noticed the clash because "runc" seemed familiar.
- tkuraku 6y agoinstead of runc, I think ccrun would be a good name. cc is usually the c compiler so ccrun would make sense and be short and explicit.
- alcover 6y ago'ccrun' is nice, thanks. 'crun' would work also.
- paulfurtado 6y agocrun is actually a project that competes with runc. runc (run container) is implemented in go, and crun is a mostly drop-in reimplementation of it in C that is more faster and simpler, it's currently gaining traction in rhel/centos/fedora and suse linux as it was first to implement newer features such as cgroup v2.
- ljm 6y agoCompiling and running C code in a single command (without using a Makefile/build system, etc. but by pulling a binary from Homebrew or whatever) feels like a 10x engineering goal, so I therefore put forward: 10cc As a bonus, it can output "I don't like C code, I love it" in its help/version docs.
- deleted 6y ago[deleted]
- crazypython 6y agoYou could rename it to "run.c" for "run dot c file." Bash supports many special characters in command names.