From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: failed autoload
Date: Sun, 6 Jul 2003 21:15:24 +0000 [thread overview]
Message-ID: <1030706211524.ZM17053@candle.brasslantern.com> (raw)
In-Reply-To: <11693.1057139730@csr.com>
On Jul 2, 10:55am, Peter Stephenson wrote:
} Subject: Re: PATCH: failed autoload
}
} So it seems to me likely that this got changed incorrectly to flag `no
} code present but no error' instead of `failed to load function, error'.
}
} Please contradict if you think my logic is wrong.
The difference since the patch mainly seems to be that the autoloaded
function remains undefined (and hence zsh will [attempt to] autoload it
again and again), rather than becoming defined as a no-op function.
Suppose you're calling the failing function in a loop. Now you'll get
the error repeatedly, as often as the loop manages to keep running,
rather than only once.
schaefer<509> repeat 7 breakthis
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
breakthis:3: parse error near `\n'
On the other hand, that's what happens even in older zsh with "function
definition file not found" so I'm not sure it's worth preserving the old
behavior.
next prev parent reply other threads:[~2003-07-06 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 18:25 Peter Stephenson
2003-07-02 3:59 ` Bart Schaefer
2003-07-02 9:55 ` Peter Stephenson
2003-07-06 21:15 ` Bart Schaefer [this message]
2003-07-07 9:40 ` Peter Stephenson
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=1030706211524.ZM17053@candle.brasslantern.com \
--to=schaefer@brasslantern.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).