From: Zefram <zefram@fysh.org>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: Bug#190948: Violation against The Single UNIX ? Specification, Version 2
Date: Thu, 15 May 2003 10:37:15 +0100 [thread overview]
Message-ID: <20030515093715.GC16886@fysh.org> (raw)
In-Reply-To: <82.1052990223@csr.com>
Peter Stephenson wrote:
>/* ZLE entry point pointers. They are defined here because the initial *
> * values depend on whether ZLE is linked in or not -- if it is, we *
> * avoid wasting space with the fallback functions. No other source *
> * file needs to know which modules are linked in. */
>
>Except we don't avoid wasting space with the fallback functions, they
>are defined unconditionally. Anyone remember what's happening?
I wrote that comment. The intent was as described, and I have a mental
image of the fallback functions being in an appropriate conditional
section. I remember adding mechanism to the build process to make that
information available to the preprocessor. If the fallback functions
are no longer conditionally compiled, it'll be an accidental change,
unless I got it wrong to start with.
-zefram
next prev parent reply other threads:[~2003-05-15 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030427130703.GB12714@verso.st.jyu.fi>
2003-05-14 11:07 ` Bug#190948: Violation against The Single UNIX ® " Oliver Kiddle
2003-05-14 11:46 ` Bug#190948: Violation against The Single UNIX R " Borzenkov Andrey
2003-05-14 12:40 ` Bug#190948: Violation against The Single UNIX ® " Peter Stephenson
2003-05-14 12:57 ` Bug#190948: Violation against The Single UNIX ? " Zefram
2003-05-14 14:14 ` Peter Stephenson
2003-05-14 14:20 ` Peter Stephenson
2003-05-15 9:17 ` Peter Stephenson
2003-05-15 9:37 ` Zefram [this message]
2003-05-15 9:49 ` 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=20030515093715.GC16886@fysh.org \
--to=zefram@fysh.org \
--cc=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).