unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>, help-gnu-emacs@gnu.org
Subject: RE: `if' in Elisp (was: Re: title-case function)
Date: Sun, 21 Apr 2019 12:34:55 +0000 (UTC)	[thread overview]
Message-ID: <bc9552d1-305f-426d-ada1-1413cef98174@default> (raw)
In-Reply-To: <86lg03lkep.fsf_-_@zoho.eu>

> >> Do you mean using progn for the ELSE in the
> >> if expression? From the documentation on
> >> `if':
> >> (if COND THEN ELSE...)
> >> THEN must be one expression, but ELSE... can
> >> be zero or more expressions.
> > So yeah, progn is unnecessary.
> 
> Unbelievable, when/how did this happen?!

After Lisp 1.5 and before Common Lisp v1 - 1970s probably.
For Emacs Lisp, it's been the case since Day One, I believe.

http://www.softwarepreservation.org/projects/LISP/book/LISP%201.5%20Programmers%20Manual.pdf

https://en.wikipedia.org/wiki/Common_Lisp_the_Language

http://www.math.utah.edu/docs/info/elisp_10.html#SEC110



  reply	other threads:[~2019-04-21 12:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21  3:56 title-case function Paul W. Rankin
2019-04-21  5:29 ` Emanuel Berg
2019-04-21  6:40   ` Paul W. Rankin
2019-04-21 10:31     ` `if' in Elisp (was: Re: title-case function) Emanuel Berg
2019-04-21 12:34       ` Drew Adams [this message]
2019-04-21 14:02         ` Emanuel Berg
2019-04-21  5:57 ` title-case function Eli Zaretskii
2019-04-21  6:10   ` Emanuel Berg
2019-04-21  6:45   ` Paul W. Rankin
2019-04-21  7:20     ` Eli Zaretskii
2019-04-21  5:57 ` Jean-Christophe Helary
2019-04-21 12:45   ` Paul W. Rankin
2019-04-21 12:59     ` Jean-Christophe Helary
2019-04-21 13:25       ` Paul W. Rankin
2019-04-21 13:58       ` the English language part 2 (was: Re: title-case function) Emanuel Berg
2019-04-21 14:23         ` the English language part 2 Ralph Seichter
2019-04-21 14:32           ` Emanuel Berg
2019-04-21 14:42             ` Ralph Seichter
2019-04-21 15:08               ` Emanuel Berg
2019-04-21 15:21                 ` Ralph Seichter
2019-04-22  4:13                 ` Marcin Borkowski
2019-04-22  7:55                   ` Paul W. Rankin
2019-04-22 21:21                     ` Emanuel Berg
2019-04-22 21:31                   ` Emanuel Berg
2019-04-25 22:58                   ` Europe in 1648 (was: Re: the English language part 2) Emanuel Berg
2019-04-26 13:40                     ` Ralph Seichter
2019-04-27 21:16                       ` Emanuel Berg
2019-04-29  3:26                         ` Europe in 1648 Van L
2019-04-21 15:22             ` the English language part 2 Drew Adams
2019-04-21 15:38               ` Jean-Christophe Helary
2019-04-21 16:16               ` Emanuel Berg
2019-04-21 13:45     ` title-case function Emanuel Berg
2019-04-21 13:37   ` the English language, again (was: Re: title-case function) Emanuel Berg
2019-04-21 13:38   ` Emanuel Berg
2019-04-22 16:41     ` Robert Thorpe
2019-04-22 21:44       ` Emanuel Berg
2019-04-23  2:35         ` Emanuel Berg
2019-04-24 11:56           ` the English language, again Van L

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc9552d1-305f-426d-ada1-1413cef98174@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).