From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zefram <A.Main@dcs.warwick.ac.uk>
Cc: hzoli@cs.elte.hu, zsh-workers@math.gatech.edu
Subject: Re: Sick macros (was: Action, not words (Re: bug (?) in 3.0-pre1))
Date: Tue, 2 Jul 1996 12:19:14 -0700 [thread overview]
Message-ID: <960702121917.ZM4663@candle.brasslantern.com> (raw)
In-Reply-To: Zefram <A.Main@dcs.warwick.ac.uk> "Re: Sick macros (was: Action, not words (Re: bug (?) in 3.0-pre1))" (Jul 2, 7:24pm)
On Jul 2, 7:24pm, Zefram wrote:
} Subject: Re: Sick macros (was: Action, not words (Re: bug (?) in 3.0-pre1)
}
} I think the size of the resulting patch should not be a consideration.
I don't either, now that I've convinced people this is a good idea. :-)
Before, I didn't want to scare anyone off by making this look like a
major code change.
} >I know for a fact that AIX could not handle
} >an `if (x,y)' construct we used in zmail, forcing us to rewrite it
} >as `if (x?0:y)'
}
} Curious. It's a perfectly legal expression, so any compiler that can't
} grok it is broken.
Oh, the compiler grokked it, but then generated buggy assembly code so that
it didn't work right.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
prev parent reply other threads:[~1996-07-02 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-28 17:12 bug (?) in 3.0-pre1 gene
1996-06-28 17:50 ` Zoltan Hidvegi
1996-06-28 19:04 ` Steven L Baur
1996-06-29 19:13 ` Bart Schaefer
1996-06-30 16:13 ` Zoltan Hidvegi
1996-06-30 19:21 ` Bart Schaefer
1996-06-30 21:50 ` Action, not words (Re: bug (?) in 3.0-pre1) Bart Schaefer
1996-07-02 7:24 ` Sick macros (was: Action, not words (Re: bug (?) in 3.0-pre1)) Zefram
1996-07-02 17:52 ` Bart Schaefer
1996-07-02 18:24 ` Zefram
1996-07-02 19:19 ` Bart Schaefer [this message]
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=960702121917.ZM4663@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=hzoli@cs.elte.hu \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).