unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel <emacs-devel@gnu.org>, Pip Cet <pipcet@gmail.com>,
	Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: 31395511: "Don’t attempt to modify constant strings"
Date: Sat, 6 Jun 2020 12:41:18 +0100	[thread overview]
Message-ID: <CALDnm528TmLkUqoSguBia+kPMeAMSs9=+AgT_Abd1N1-X8kA3g@mail.gmail.com> (raw)
In-Reply-To: <58642244-da07-c96d-21d5-d7d46714678d@cs.ucla.edu>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

On Sat, Jun 6, 2020 at 2:43 AM Paul Eggert <eggert@cs.ucla.edu> wrote:

> On 6/5/20 4:19 PM, João Távora wrote:
> > I totally agree it is
> > undefined behaviour to change structure of literals (quoted or
> > self-evaluating objects), also in Common Lisp, because compilers are
> > probably allowed to reuse parts of the internal structure of such
> > objects.  But that's a far cry from having two different manifestations
> > of `equal` such objects _be_ the same object, but only for compiled
> > code.
>
> I don't understand this remark, as the idea that "compilers are allowed to
> reuse
> parts" necessarily implies that (eq "a" "a") can be t if the compiler
> decides to
> reuse the string.


Depending on the implementation of sequences, it could reuse only the
later parts of the sequences to maintain uniqueness and still have


> Certainly in Common Lisp (eq "Foo" "Foo") might be true or
> false (this specific example is called out in CLtL 6.3).
>

I stand corrected.  I was simply mistaken :-)

João

[-- Attachment #2: Type: text/html, Size: 1624 bytes --]

  parent reply	other threads:[~2020-06-06 11:41 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 21:52 31395511: "Don’t attempt to modify constant strings" João Távora
2020-06-03 22:41 ` Paul Eggert
2020-06-03 22:52   ` Pip Cet
2020-06-03 23:20     ` Paul Eggert
2020-06-03 23:20     ` Basil L. Contovounesios
2020-06-03 22:41 ` Pip Cet
2020-06-03 23:08   ` Basil L. Contovounesios
2020-06-03 23:31     ` Basil L. Contovounesios
2020-06-03 23:48   ` João Távora
2020-06-04  0:43     ` Paul Eggert
2020-06-04  1:19       ` Paul Eggert
2020-06-04  7:26         ` Pip Cet
2020-06-04 11:11           ` Basil L. Contovounesios
2020-06-04 19:46             ` Paul Eggert
2020-06-04 20:25               ` João Távora
2020-06-04 20:29                 ` Paul Eggert
2020-06-04 21:21                   ` Drew Adams
2020-06-04 20:43               ` Pip Cet
2020-06-04 21:27                 ` Stefan Monnier
2020-06-04 21:42                   ` Pip Cet
2020-06-04 23:10                 ` Paul Eggert
2020-06-05  2:09                   ` Clément Pit-Claudel
2020-06-05  6:44                     ` Paul Eggert
2020-06-05 12:44                       ` Stefan Monnier
2020-06-05 17:01                     ` Drew Adams
2020-06-05  9:48                   ` Pip Cet
2020-06-05 18:37                     ` Paul Eggert
2020-06-04 22:33               ` Basil L. Contovounesios
2020-06-05 15:25       ` João Távora
2020-06-05 17:14         ` Dmitry Gutov
2020-06-05 23:19           ` João Távora
2020-06-05 23:32             ` Dmitry Gutov
2020-06-06  1:34               ` FW: " Drew Adams
2020-06-06  0:23             ` Drew Adams
2020-06-06  1:43             ` Paul Eggert
2020-06-06  4:06               ` Richard Stallman
2020-06-06 11:41               ` João Távora [this message]
2020-06-06 11:47                 ` João Távora
2020-06-04  4:38     ` Pip Cet
2020-06-04  9:31       ` João Távora

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='CALDnm528TmLkUqoSguBia+kPMeAMSs9=+AgT_Abd1N1-X8kA3g@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@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).