unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sam Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] * etc/NEWS: Document incompatibilities introduced by record types.
Date: Wed, 13 Dec 2017 10:41:12 -0500	[thread overview]
Message-ID: <lzd13ihbzb.fsf@gnu.org> (raw)
In-Reply-To: jwvtvwvpp2z.fsf-monnier+gmane.emacs.devel@gnu.org

> * Stefan Monnier <zbaavre@veb.hzbagerny.pn> [2017-12-12 17:20:29 -0500]:
>
>> If programmers are not supposed to do it, let's detect it and report
>> an error when they try.  That way, they will know it's an error as
>> soon as they try, rather than needing to debug it to find out it's an error.
>
> When was the last time you saw a user try to redefine the
> "integer" type?
> [ I'll be happy to hear about cases in other languages than Elisp,
>   since otherwise it's going to be depressingly silent I'm afraid.  ]

What's so special about "integer"?
How many other built-in types does Emacs Lisp have?
Can you list them all by heart? Can everyone?
What about many different packages which may redefine each other's
types?  Especially since Emacs Lisp does not have the Common Lisp-style
package system, and it does not enforce the prefix conventions.

It seems to me that warning on redefining a type (or defining a type
with a name which already names a type) is a very good idea.
Emacs Lisp already warns on redefining functions with a different
signature.  Why not warn about types?

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org
http://camera.org http://memri.org http://www.memritv.org
At war time "salt of the earth" becomes "cannon fodder".




  reply	other threads:[~2017-12-13 15:41 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 21:37 [PATCH] * etc/NEWS: Document incompatibilities introduced by record types Philipp Stephani
2017-12-11 22:25 ` Clément Pit-Claudel
2017-12-21 16:35   ` Philipp Stephani
2017-12-12  3:21 ` Stefan Monnier
2017-12-12 19:13   ` Clément Pit-Claudel
2017-12-12 20:45     ` Stefan Monnier
2017-12-13 23:00       ` Richard Stallman
2017-12-14 14:08         ` Stefan Monnier
2017-12-14 22:16           ` Richard Stallman
2017-12-14 23:41             ` Stefan Monnier
2017-12-15 21:25               ` Richard Stallman
2017-12-14 22:17           ` Richard Stallman
2017-12-22 10:06             ` Eli Zaretskii
2017-12-21 17:29       ` Philipp Stephani
2017-12-13 23:00     ` Richard Stallman
2017-12-14 14:07       ` Stefan Monnier
2017-12-12 22:06   ` Richard Stallman
2017-12-12 22:20     ` Stefan Monnier
2017-12-13 15:41       ` Sam Steingold [this message]
2017-12-13 16:30         ` Stefan Monnier
2017-12-13 23:03       ` Richard Stallman
2017-12-14 14:13         ` Stefan Monnier
2017-12-13  1:03     ` Stefan Monnier
2017-12-13  1:12       ` Noam Postavsky
2017-12-13  1:29         ` Stefan Monnier
2017-12-13 17:40           ` Stephen Leake
2017-12-13 23:02           ` Richard Stallman
2017-12-14 14:12             ` Stefan Monnier
2017-12-14 22:16               ` Richard Stallman
2017-12-14 22:16               ` Richard Stallman
2017-12-21 17:34         ` Philipp Stephani
2017-12-21 18:43           ` Stefan Monnier
2017-12-22 18:46             ` Richard Stallman
2017-12-22 19:39               ` [SUSPECTED SPAM] " Stefan Monnier
2017-12-23 14:56                 ` Richard Stallman
2017-12-23 14:56                 ` make-record Richard Stallman
2017-12-23 15:53                   ` make-record Stefan Monnier
2017-12-24 20:35                     ` make-record Richard Stallman
2017-12-26  2:43                       ` make-record Stefan Monnier
2017-12-26 19:41                         ` make-record Richard Stallman
2017-12-12 22:05 ` [PATCH] * etc/NEWS: Document incompatibilities introduced by record types Richard Stallman

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=lzd13ihbzb.fsf@gnu.org \
    --to=sds@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).