From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] * etc/NEWS: Document incompatibilities introduced by record types. Date: Thu, 14 Dec 2017 17:16:19 -0500 Message-ID: References: <20171211213729.41411-1-phst@google.com> Reply-To: rms@gnu.org NNTP-Posting-Host: blaine.gmane.org Content-Type: text/plain; charset=Utf-8 X-Trace: blaine.gmane.org 1513289791 26116 195.159.176.226 (14 Dec 2017 22:16:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 14 Dec 2017 22:16:31 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 14 23:16:27 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ePbnm-0006Y9-Sf for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2017 23:16:26 +0100 Original-Received: from localhost ([::1]:43254 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePbnt-0001Qm-T2 for ged-emacs-devel@m.gmane.org; Thu, 14 Dec 2017 17:16:33 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39475) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePbnj-0001QO-4y for emacs-devel@gnu.org; Thu, 14 Dec 2017 17:16:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePbnh-0000wp-Vx for emacs-devel@gnu.org; Thu, 14 Dec 2017 17:16:23 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42078) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePbnf-0000ug-OJ; Thu, 14 Dec 2017 17:16:19 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1ePbnf-0002LO-AI; Thu, 14 Dec 2017 17:16:19 -0500 In-reply-to: (message from Stefan Monnier on Thu, 14 Dec 2017 09:12:44 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221069 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > Since we agree that defining these symbols as record types should not > > be done, let's make it easier for programmers to avoid doing that. > I won't get in the way of someone else doing that, *as long as* it's > done via compilation-time (or even load-time) checks rather than > run-time checks (i.e. not in make-record). We should do what is necessary to solve the problem. Let's see what is needed to prevent the problem. The issue at hand is that defining a record called 'hashtable' or 'integer' can alter how built-in types print. That is a pitfall and we should put a fence around it. What are the concrete actions that would have this result? Would using 'hashtable' or 'integer' in make-record cause that to occur? -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org) Skype: No way! See https://stallman.org/skype.html.