From: haahr@mv.us.adobe.com (Paul Haahr)
To: richard@harlequin.co.uk
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: else if not (Re: wishlist)
Date: Wed, 26 May 1993 13:24:51 -0400 [thread overview]
Message-ID: <9305261724.AA01005@astro.mv.us.adobe.com> (raw)
> The if/else `problem' has always struck me as really stupid.
the only if/else problem in rc is that it's not compatible with td's rc.
the reason is that if not semantics are awful, as is acknowledged in the
rc paper. Byron introduced this one change because he thought it was an
improvement worth being incompatible with the plan 9 version. i agree
with him; the last time we hashed this out on the list it seemed that
was the consensus.
> BCPL and
> LISP get it right.
that's a matter of opinion. Byron and i picked scheme's cond semantics
for es, because we thought that was right.
paul
next reply other threads:[~1993-05-26 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-05-26 17:24 Paul Haahr [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-05-26 6:57 wishlist Bengt KLEBERG
1993-05-26 9:34 ` else if not (Re: wishlist) Richard Brooksby
1993-05-26 17:52 ` Chris Siebenmann
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=9305261724.AA01005@astro.mv.us.adobe.com \
--to=haahr@mv.us.adobe.com \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=richard@harlequin.co.uk \
/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.
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).