From owner-freebsd-hackers@FreeBSD.ORG  Thu May 29 04:15:26 2008
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5124A106567A
	for <freebsd-hackers@freebsd.org>; Thu, 29 May 2008 04:15:26 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 5D0438FC0C
	for <freebsd-hackers@freebsd.org>; Thu, 29 May 2008 04:15:26 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from zion.baldwin.cx (server.baldwin.cx [208.65.91.234])
	by elvis.mu.org (Postfix) with ESMTP id AA6E11A4D7C;
	Wed, 28 May 2008 21:15:25 -0700 (PDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-hackers@freebsd.org
Date: Thu, 29 May 2008 00:04:41 -0400
User-Agent: KMail/1.9.7
References: <20080309152712.42752293@bhuda.mired.org>
	<18489.32903.477434.465037@gromit.timing.com>
	<20080525154537.GB1026@lizard.fafoe.narf.at>
In-Reply-To: <20080525154537.GB1026@lizard.fafoe.narf.at>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200805290004.41653.jhb@freebsd.org>
Cc: Stefan Farfeleder <stefan@fafoe.narf.at>, hackers@freebsd.org,
	Mike Meyer <mwm@mired.org>, John E Hein <jhein@timing.com>
Subject: Re: Why doesn't autoconf like our /bin/sh?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2008 04:15:26 -0000

On Sunday 25 May 2008 11:45:37 am Stefan Farfeleder wrote:
> 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."

Actually, the bash way seems more intuitive.  And it does say "the current 
sequentional line number within a ... function before it executes each 
command"

The "within a function" implies that this property goes inside of functions 
instead of forcing all commands in a function to use the starting line of the 
function which is what you are saying?

-- 
John Baldwin