Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: [Help-bash] extdebug not providing expected results with declare -F Date: Wed, 22 Jul 2015 10:39:49 -0400 Lines: 19 Approved: bug-bash@gnu.org Message-ID: References: NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1437576028 24762 208.118.235.17 (22 Jul 2015 14:40:28 GMT) X-Complaints-To: action@cs.stanford.edu Cc: help-bash@gnu.org To: bug-bash@gnu.org Envelope-to: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: aioe.org gnu.bash.bug:11251 On Wed, Jul 22, 2015 at 07:26:54AM -0700, Michael Convey wrote: > According to man bash: > > The -F option to declare or typeset will list the function names only (and > optionally the > ?????? > source file and line number, if the extdebug shell option is enabled). I have no comment on the extdebug part, but while perusing the man page to find this section, I came across: Note that shell functions and variables with the same name may result in multiple identically-named entries in the environment passed to the shell's children. Care should be taken in cases where this may cause a problem. I believe this section is no longer correct, as exported functions now use BASH_FUNC_funcname%% in the environment.