zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Debugging of dynamocally defined functions
Date: Fri, 06 Jul 2001 11:22:36 +0100	[thread overview]
Message-ID: <Tc0a88d01549467c4a9@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Fri, 06 Jul 2001 11:56:44 +0200." <200107060956.LAA12775@beta.informatik.hu-berlin.de>

Sven Wischnowsky wrote:
> Hm, could we change it so that it saves the line number of the script or
> surrounding function?

What does the principle of least surprise give here?  Here's the current
behaviour.

  % cat fn
  print fn has now been executed.  Ecky thump.
  
  fn2() {                
  print $LINENO  
  }
  % autoload fn
  % fn
  fn has now been executed.  Ecky thump.
  % fn2
  1

(remember that the `fn2() {' line is numbered zero).

If you used the file it was in, you would get a line number of 4 in a 1
line function, together (with xtrace) with the name of that function.  What
you really want to know, I suppose, is the name of the function, the name
of the file it was read from, and the line number in that file.  That could
probably be arranged.  But it does mean an increased number of special
cases --- are we autoloading or running a dot file, if so, are we defining
a function which is not the one we are autoloading --- so it's not that
simple.

Alternatively, we forget about using line numbers on input and define them
when parsing, so they relate to the `which' output.  That's a big change,
and probably less useful since it's the original file you're going to be
editing.  I don't think it's worth remembering both.

By the way, you can use the trick of

  eval "$(which compdef)"

to sync the line numbers with the which output.  At least I hope so --- if
this goes screwy there's a bug in text.c.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  reply	other threads:[~2001-07-06 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05  5:33 Andrej Borsenkow
2001-07-06  9:56 ` Sven Wischnowsky
2001-07-06 10:22   ` Peter Stephenson [this message]
2001-07-07 23:30 ` Bart Schaefer
2001-07-08 22:26   ` Peter Stephenson
2001-07-09 10:38   ` Peter Stephenson
2001-07-09 14:52   ` Peter Stephenson
2001-07-09 16:30     ` Peter Stephenson
2001-07-09 16:50     ` Bart Schaefer
2001-07-09 17:32       ` Peter Stephenson
2001-07-09 18:24         ` Bart Schaefer
2001-07-09 18:36           ` Peter Stephenson
2001-07-09 19:19             ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Tc0a88d01549467c4a9@mailsweeper01.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).