Re: possible bug with $@ and and non-standard IFS

2009-08-05 Thread JR Rothschild
> If you use nd="${dh}$*" before resetting IFS, you'll get the output you > in bash-3.0 through bash-4.0. But I don't in Bourne shell, I get smith0.0. So neither construct works in a portable manner. :( JR

Re: possible bug with $@ and and non-standard IFS

2009-08-04 Thread JR Rothschild
Apparently, I have run into an area of some controversy (or at least some disagreement) On my Solaris 10 box, ksh thinks that the expected output should be smith::0.0 sh -> smith:0.0 (an old version of bash) -> smith: 0.0 dtksh-> smith: 0.0 I don't think this will get solved anytime soon. :) T

Re: possible bug with $@ and and non-standard IFS

2009-08-04 Thread Chet Ramey
JR Rothschild wrote: > Hi, > In either version 3.1.17 (SUSE 10) or 3.2.25 (RHEL 5.3), with $DISPLAY > set to :0.0 > the following script gives unexpected results.(It works with version > 3.0.15 - RHEL4.6) The echo should print out > > smith:0.0 It shouldn't display that; there are different bugs

possible bug with $@ and and non-standard IFS

2009-08-03 Thread JR Rothschild
Hi, In either version 3.1.17 (SUSE 10) or 3.2.25 (RHEL 5.3), with $DISPLAY set to :0.0 the following script gives unexpected results.(It works with version 3.0.15 - RHEL4.6) The echo should print out smith:0.0 instead of smith 0.0 #!!/bin/bash dh=smith oldIFS=$IFS IFS=: set $DISPLAY nd="${dh}: