From owner-freebsd-hackers@FreeBSD.ORG Sun May 25 15:58:39 2008 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E2AB1065677 for ; Sun, 25 May 2008 15:58:39 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (daffy.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 22EEB8FC15 for ; Sun, 25 May 2008 15:58:39 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id m4PFwab9076279; Sun, 25 May 2008 09:58:36 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.2/8.14.2) with ESMTP id m4PFwYQ7088807; Sun, 25 May 2008 09:58:34 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.2/8.14.2/Submit) id m4PFwYwJ088804; Sun, 25 May 2008 09:58:34 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18489.36010.220739.891583@gromit.timing.com> Date: Sun, 25 May 2008 09:58:34 -0600 From: John E Hein To: Stefan Farfeleder In-Reply-To: <20080525154537.GB1026@lizard.fafoe.narf.at> References: <20080309152712.42752293@bhuda.mired.org> <20080516074433.GA1032@lizard.fafoe.narf.at> <20080516101143.3545937c@bhuda.mired.org> <20080516141307.GB1032@lizard.fafoe.narf.at> <18489.32903.477434.465037@gromit.timing.com> <20080525154537.GB1026@lizard.fafoe.narf.at> X-Mailer: VM 7.19 under Emacs 22.1.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: hackers@freebsd.org, Mike Meyer 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 May 2008 15:58:39 -0000 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.