Chris Linton-Ford writes: > It might be helpful to consider the shells' dual nature as a) a > scripting medium and b) an interactive environment. Surely there is no > engineering reason why a shell could not be coded to have only a strict > superset of /sbin/sh's commands, thus making scripts compatible.
What's the superset of this? $ /sbin/sh -c 'foo=a; echo b | read foo; echo $foo' a $ /usr/bin/ksh93 -c 'foo=a; echo b | read foo; echo $foo' b Shawn Walker writes: > I still do not believe that something cannot be done to address the issue. At least in some cases, the "something" would have to be an assumption that the unresolvable differences are simply unimportant and will either have no effect on users or will have effects that we just don't care about. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
