Re: Bug#95430 acknowledged by developer (Re: Bug#95430: ash: word-splitting changes break shell scripts)

[Shaul Karl <shaulka@bezeqint.net>]

> Herbert Xu <herbert@gondor.apana.org.au> writes:
> 
> > Not only does that show that Solaris 2.6's shell does not set IFS,
> 
> windlord:~> printenv IFS
> windlord:~> /bin/sh -c 'echo x-${IFS}-x'
> x- -x
> windlord:~> uname -a
> SunOS windlord.stanford.edu 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-1
> 
> Looks set to me, although it appears to be set incorrectly.
> 



Incorrectly? Looks to me the same as with bash:
[16:24:40 tmp]$ printenv IFS
[16:24:46 tmp]$ bash -c 'echo x-${IFS}-x'
x- -x
[16:24:48 tmp]$ bash --version
GNU bash, version 2.05.0(1)-release (i386-pc-linux-gnu)
Copyright 2000 Free Software Foundation, Inc.
[16:27:28 tmp]$ 

Ah, something might be wrong with the above tests:
[16:35:41 tmp]$ set | grep IFS
IFS=$' \t\n'
[16:35:59 tmp]$ 



> Solaris's /bin/sh isn't a particularly good example, as it's one of the
> most completely broken Bourne shells shipped with a modern OS.  It doesn't
> even try to be POSIX-compliant.
> 
> -- 
> Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 

-- 
	
	Shaul Karl <shaulka@bezeqint.net>