Re: Non-POSIX shells

[Sander Vesik <Sander Vesik Sun COM>]

On Tue, 5 Mar 2002, ERDI Gergo wrote:

> On Tue, 5 Mar 2002, Sander Vesik wrote:
> 
> >   Utilities
> >      If the behavior required by POSIX.2, POSIX.2a, XPG4, SUS, or
> >      SUSv2  conflicts  with  historical Solaris utility behavior,
> >      the original Solaris version of the utility is unchanged;  a
> >      new version that is standard-conforming has been provided in
> >      /usr/xpg4/bin. For applications wishing to take advantage of
> >      POSIX.2,  POSIX.2a,  XPG4,  SUS, or SUSv2 features, the PATH
> >      (sh or ksh) or path (csh) environment  variables  should  be
> >      set  with  /usr/xpg4/bin  preceding any other directories in
> >      which  utilities   specified  by  those  specifications  are
> >      found, such as /bin, /usr/bin, /usr/ucb, and /usr/ccs/bin.
> 
> you realize, of course, that this is useless for shell scripts when you
> need to write something in the shebang line.
> 

Umm... no - you just can't realy on anything beyond the capabilities
provided by Bourne shell (or equivalent) in shell scripts that have to be
portable. If it is not a shell script that gets run directly, just call it
shellscript.sh.in and have configure replace the #! POSIX_SHELL@ at the
top or something similar...

> -- 
>    .--= ULLA! =---------------------.   `We are not here to give users what
>    \     http://cactus.rulez.org     \   they want'  -- RMS, at GUADEC 2001
>     `---= cactus cactus rulez org =---'
> If Old MacDonald had a computer, would it use Eee-aye-eee I/O?
> 

	Sander

	I see a dark sail on the horizon
	Set under a dark cloud that hides the sun
	Bring me my Broadsword and clear understanding