Messages in this thread | | | Date | Sun, 21 Mar 1999 13:29:33 -0500 (EST) | From | Alexander Viro <> | Subject | Re: #!perl - alternative path to script interpreters - patch to 2.2 |
| |
On Sun, 21 Mar 1999, Albert D. Cahalan wrote:
> > Alexander Viro writes: > > > And script written under Linux and using that feature will break > > *everywhere* else. Fun, fun... > > That would not be a Linux problem.
Bullshit. Software locked on *any* platform is evil, for a lot of reasons, starting from the fact that it locks the platform in question too. Recall your own comments re inability to separate /proc/<pid>/ stuff from the rest of /proc without *major* breakage. The same reason why every additional function in export list is the call for trouble, just that with userland-visible stuff it's even worse (modules breakage is nasty, but it's better than userland breakage). Even with modules we are deep in it - struct file_operations is the holy cow that can't be touched without breaking tons of 3rd-party hardware drivers. Look at the current mess with ioctls. Like it? Me neither.
> >>>> It is more elegant to treat word after #! as a name of language... > >>> > >>> It is *completely* non-portable. Moreover, it will be useless for > >>> situations when different names are used for different versions of > >>> aforementioned awk (gawk vs. mawk). > > One could have the kernel substitute any pathname for any other > pathname when executing a script.
Or you can do it with sed when you install the software.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |