From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: failed autoload
Date: Wed, 2 Jul 2003 03:59:41 +0000 [thread overview]
Message-ID: <1030702035941.ZM956@candle.brasslantern.com> (raw)
In-Reply-To: <10636.1057083914@csr.com>
On Jul 1, 7:25pm, Peter Stephenson wrote:
}
} It can't be correct that if an autoload fails beacause of a syntax error
} that the function returns 0.
}
} I don't see how it can be useful to define the function with an empty
} function body, either.
}
} if (!prog)
} - prog = &dummy_eprog;
I'm sure there was a reason for this, at one time. It was introduced in
zsh-workers/9332 by Sven, with the log message "Use word code instead of
structs for passing executable chunks around."
next prev parent reply other threads:[~2003-07-02 3:59 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 [this message]
2003-07-02 9:55 ` Peter Stephenson
2003-07-06 21:15 ` Bart Schaefer
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=1030702035941.ZM956@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).