On 11-May-2005, martin f krafft wrote: > also sprach Ben Finney <ben@benfinney.id.au> [2005.05.11.0307 +0200]: > > To what extent should that be used? Is it reasonable to do it for > > *any* shebang line? '#!/usr/bin/env make'? '#!/usr/bin/env bash'? > > Are there any downsides? > > Performance. That's a potential downside, yes. Invoking an extra process, followed by a search through the PATH variable locations. > Debian standardises executable locations, so there is no need for > lookup. The context of the '#!/usr/bin/env python' trick extends beyond Debian though; the whole point is that a lookup will work in environments where the location of the executable *isn't* the standard one. If we could safely assume our scripts would only ever be run on Debian systems, we could dispense with a great many portability tricks. -- \ "Two paradoxes are better than one; they may even suggest a | `\ solution." -- Edward Teller | _o__) | Ben Finney <ben@benfinney.id.au>
Attachment:
signature.asc
Description: Digital signature