[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: configure.lineno?
From: |
Eric Siegerman |
Subject: |
Re: configure.lineno? |
Date: |
Wed, 7 Jan 2004 15:39:25 -0500 |
User-agent: |
Mutt/1.2.5i |
On Wed, Jan 07, 2004 at 10:40:30AM -0800, Paul Eggert wrote:
> 5) Dynamically test whether $LINENO is working inside shell functions,
> and prepend the function name to $LINENO if the bug is present.
A variant of this: always prepend the function name ("main" or something
if in the mainline). Besides helping with the relative-LINENO thing,
that:
- is generally useful, as it is in compiler error messages to
have both function name and (file-relative) line number
- ensures that the message prologue always has the same format,
whether or not the message came from a function, and whether
or not the script is running in a broken shell
Then mention in the docs that the line number is
function-relative on older shells.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
It must be said that they would have sounded better if the singer
wouldn't throw his fellow band members to the ground and toss the
drum kit around during songs.
- Patrick Lenneau
- Re: configure.lineno?, (continued)
- Re: configure.lineno?, Eric Sunshine, 2004/01/07
- Re: configure.lineno?, Daniel Reed, 2004/01/07
- Re: configure.lineno?, Eric Sunshine, 2004/01/07
- Re: configure.lineno?, Daniel Reed, 2004/01/08
- Re: configure.lineno?, Alexandre Duret-Lutz, 2004/01/08
- Re: configure.lineno?, Richard Dawe, 2004/01/09
- Re: configure.lineno?, Eric Sunshine, 2004/01/10
Re: configure.lineno?, Eric Sunshine, 2004/01/06
Re: configure.lineno?, bonzini, 2004/01/07
Re: configure.lineno?, Eric Sunshine, 2004/01/10