unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Should records be able to mimic primitive types?
Date: Mon, 12 Jun 2017 20:00:31 +0300	[thread overview]
Message-ID: <83tw3l3zv4.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRwhJzCXedwKjGRJu9Xtatsf1ymytk6oeXnQOkvjCvMEA@mail.gmail.com> (message from Philipp Stephani on Mon, 12 Jun 2017 15:07:16 +0000)

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 12 Jun 2017 15:07:16 +0000
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
>  It's okay to disagree, but these have been the principles underlying
>  Emacs development since about forever, so please try to be consistent
>  with them as long as they are followed. I don't think a case for
>  making Emacs Lisp a more restricted development environment than it is
>  now will gain many supporters. E.g., even the move to make characters
>  a special data type separate from integers, something the XEmacs
>  actually did, was rejected by Emacs.
> 
> That's not my intention. What I have in mind is to raise more signals in cases where users use Emacs
> functions incorrectly instead of employing unspecified behavior.

If some usage is unequivocally wrong, can never support legitimate use
cases, and the defenses are not too expensive, then I think this could
be okay.  But we need to be careful not to disallow legitimate, though
perhaps somewhat dangerous practices.  Emacs's tradition is to trust
the Lisp programmers not to shoot themselves in the foot, so we
generally prefer to err on that side of the line, when in doubt.
Punishing the innocent on behalf of possibly guilty is something I
think we should try to avoid.



  reply	other threads:[~2017-06-12 17:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 22:00 Should records be able to mimic primitive types? Paul Eggert
2017-04-05  1:09 ` Stefan Monnier
2017-04-08 15:09   ` Philipp Stephani
2017-04-08 17:57     ` Stefan Monnier
2017-05-01 11:35       ` Philipp Stephani
2017-05-01 12:03         ` Stefan Monnier
2017-06-10 11:39           ` Philipp Stephani
2017-06-10 12:43             ` Eli Zaretskii
2017-06-12 15:07               ` Philipp Stephani
2017-06-12 17:00                 ` Eli Zaretskii [this message]
2017-06-12 17:15                   ` Stefan Monnier
2017-06-12 17:22                     ` Eli Zaretskii
2017-06-12 17:47                       ` Stefan Monnier
2017-06-12 17:40       ` Stefan Monnier
2017-06-16 18:42         ` Philipp Stephani
2017-06-16 19:07           ` Stefan Monnier
2017-09-24 14:47             ` Philipp Stephani
2017-09-24 16:44               ` Stefan Monnier

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=83tw3l3zv4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=p.stephani2@gmail.com \
    /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.savannah.gnu.org/cgit/emacs.git

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).