Why doesn't autoconf like our /bin/sh?

[John E Hein]

Stefan Farfeleder wrote at 17:45 +0200 on May 25, 2008:
 > On Sun, May 25, 2008 at 09:06:47AM -0600, John E Hein wrote:
 > > FWIW, it seems bash and sh report line number differently.
 > > 
 > > # grep -n ^ ~/tmp/ln
 > > 1:#!/bin/sh
 > > 2:echo f line: $LINENO
 > > 3:f()
 > > 4:{
 > > 5:echo f line: $LINENO
 > > 6:}
 > > 7:
 > > 8:f
 > > 9:echo main line: $LINENO
 > > 10:f
 > > 
 > > 
 > > # /bin/sh ~/tmp/ln
 > > f line: 2
 > > f line: 3
 > > main line: 9
 > > f line: 3
 > > 
 > > 
 > > # bash ~/tmp/ln
 > > f line: 2
 > > f line: 5
 > > main line: 9
 > > f line: 5
 > 
 > Yes, I know.  I think it is a bug in bash as SUSv3 states:
 > 
 > "Set by the shell to a decimal number representing the current
 > sequential line number (numbered starting with 1) within a script or
 > function before it executes each command."

Okay.  Not knowing more context, I guess the 'or' (script or function)
leaves things somewhat subject to interpretation.