#! /usr/bin/env considered harmful - Programming On Unix

Users browsing this thread: 2 Guest(s)
pranomostro
Long time nixers
> Not the right interpreter is found

Generally we then have to ask for the better alternatives. If we specify a path, we can never be sure it works (because none of this shit is standartized, except the location of /usr/bin/env).

> No dependencies or modules

I can't say anything about that since the most things I use scripting for is either rc or lua, where I don't happen to need modules or dynamically linking libraries. Someone smarter than me comment on this please.

> no flags

This is really stupid. This is one of the stupid unix limitatians I talked about, things that don't make any sense today but are still included.
But it applies to other shebangs as well, so I would say fuck that.

> wrong configuration of $PATH

Then your user is a moron and it is his own fault. $PATH should never be changed, only appended to.

The solutions given are both bloated and unportable. env seems like the cleaner solution to me. I don't like using tho whole path since people thought it would be a good idea to put binaries into different directories. Ugh.


Messages In This Thread
#! /usr/bin/env considered harmful - by jkl - 14-09-2016, 12:27 PM
RE: #! /usr/bin/env considered harmful - by venam - 14-09-2016, 01:04 PM
RE: #! /usr/bin/env considered harmful - by z3bra - 14-09-2016, 01:36 PM
RE: #! /usr/bin/env considered harmful - by jkl - 14-09-2016, 08:13 PM
RE: #! /usr/bin/env considered harmful - by pranomostro - 14-09-2016, 08:59 PM
RE: #! /usr/bin/env considered harmful - by z3bra - 15-09-2016, 05:40 AM
RE: #! /usr/bin/env considered harmful - by z3bra - 15-09-2016, 09:14 AM