'Paul Jarc wrote:'
>
> >#! interpreter [argument]
>
> Note that this is a doc bug; the space was never required.
> http://www.in-ulm.de/~mascheck/various/shebang/>
Ok, thanx Paul, Bob and Jim for your information - I learned a lot.
The different "usage" of the arguments by different
[EMAIL PROTECTED] (Bob Proulx) wrote:
> Paul Jarc wrote:
>> Bob Proulx wrote:
>>> One or more spaces or tabs must separate interpreter and argument.
>>
>> Note that this is a doc bug; the space was never required.
>
> I agree that there was never a need for a space after the #! which is
> to wh
Paul Jarc wrote:
> Bob Proulx wrote:
> > Found in the exec man page on some systems:
> >
> > The initial line of a script file must begin with #! as the first two
> > bytes, followed by zero or more spaces, followed by interpreter or
> >
> > interpreter argument, as in:
> >
> >
[EMAIL PROTECTED] (Bob Proulx) wrote:
> Found in the exec man page on some systems:
>
> The initial line of a script file must begin with #! as the first two
> bytes, followed by zero or more spaces, followed by interpreter or
> interpreter argument, as in:
>
>#! inter
Jens Elkner <[EMAIL PROTECTED]> wrote:
...
> Furthermore according to XBD Utility Syntax Guidelines, long option support
> (i.e. --ignore-environment, --unset) should be dropped.
An application may accept long-named options like --ignore-environment
and still be POSIX compliant. There is no reas
Jens Elkner wrote:
> 'Paul Jarc wrote:'
> > scripts are limited to only one argument in the "#!" line
> > after the interpreter.
>
> Hmm, have you any pointer to a guideline or standard for this. Currently
> I have not found anything wrt. #! interpreter arg, expect in the Solaris
> exec manpage :(
'Paul Jarc wrote:'
>
> Jens Elkner <[EMAIL PROTECTED]> wrote:
> > unfortunately env is not POSIX, or to be more specific, not "The Open Group
> > Base Specifications Issue 6 IEEE Std 1003.1, 2003 Edition" compliant on Linux.
> > (see http://www.unix-systems.org/version3/iso_std.html )
> >
> > E.g.
[EMAIL PROTECTED] (Paul Jarc) wrote:
> Jens Elkner <[EMAIL PROTECTED]> wrote:
>> Last but not least - why not
>> ...
>> static char *pointer2null = NULL;
>> ...
>> main() {
>> ...
>> if (ignore_environment)
>> environ = &pointer2null;
>
> I haven't looked at t
Jens Elkner <[EMAIL PROTECTED]> wrote:
> unfortunately env is not POSIX, or to be more specific, not "The Open Group
> Base Specifications Issue 6 IEEE Std 1003.1, 2003 Edition" compliant on Linux.
> (see http://www.unix-systems.org/version3/iso_std.html )
>
> E.g.: filename.env
> #!/usr/bin/env -i
Hi,
unfortunately env is not POSIX, or to be more specific, not "The Open Group
Base Specifications Issue 6 IEEE Std 1003.1, 2003 Edition" compliant on Linux.
(see http://www.unix-systems.org/version3/iso_std.html )
E.g.: filename.env
#!/usr/bin/env -i command args ...
should exec command with t
10 matches
Mail list logo
