Re: [patch] bashism in sh script

2003-08-14 Thread Andrew V. Samoilov
> On Fri, 1 Aug 2003, GoTaR wrote: > > > There's no thing like $[..] to evaluate expressions in POSIX sh, it's > > bash feature. sh uses $((..)) instead (and bash understands it too). > > Here comes fix. > > Does the next line work for you? I mean this: > > if (( $A < 10 )); then A="0$A"; f

Re: [patch] bashism in sh script

2003-08-14 Thread Pavel Roskin
On Fri, 8 Aug 2003, Andrew V. Samoilov wrote: > I think patch below make audio.in much more portable. Applied. > BTW, I don't see reason to substitute audio from audio.in. There is @AWK@ in audiofs_copyout(), but it's hard to notice :-) -- Regards, Pavel Roskin ___

Re: [patch] bashism in sh script

2003-08-14 Thread Pavel Roskin
On Fri, 1 Aug 2003, GoTaR wrote: > There's no thing like $[..] to evaluate expressions in POSIX sh, it's > bash feature. sh uses $((..)) instead (and bash understands it too). > Here comes fix. Does the next line work for you? I mean this: if (( $A < 10 )); then A="0$A"; fi I think it's a

Re: [patch] bashism in sh script

2003-08-10 Thread GoTaR
On Fri, Aug 08, 2003 at 03:45:11 -0400, Pavel Roskin wrote: > > There's no thing like $[..] to evaluate expressions in POSIX sh, it's > > bash feature. sh uses $((..)) instead (and bash understands it too). > > Here comes fix. > > Does the next line work for you? I mean this: > > if (( $A <

[patch] bashism in sh script

2003-08-01 Thread GoTaR
Hi! There's no thing like $[..] to evaluate expressions in POSIX sh, it's bash feature. sh uses $((..)) instead (and bash understands it too). Here comes fix. -- Tom Pala <[EMAIL PROTECTED]> diff -urN mc/vfs/extfs/audio.in mc.new/vfs/extfs/audio.in --- mc/vfs/extfs/audio.in 2002-12-13 05:4