3 ms·
You generally shouldn’t use absolute paths in your programs. That makes it dangerous for local development, and makes running two copies of the program to compa
by hinkley 2y ago
You generally shouldn’t use absolute paths in your programs. That makes it dangerous for local development, and makes running two copies of the program to compare behaviors difficult.
There’s a Venn diagram of people who don’t care enough to do that (works for me!) and people who would never think to use c-reduce. It’s not a perfect circle, but it’ll be fairly close.
- somat 2y ago> You generally shouldn’t use absolute paths in your programs. This is true, but I was enjoying the irony that there is an old sys-sdmin adage that you should only use absolute paths in your program(usually a shell script, in this environment) this is to make sure it is running exactly what you expect it to run. So always put "/usr/bin/awk" instead of just "awk" I had a co-worker once who took this as gospel. His scripts were always... interesting... to port to a new environment.