all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15122@debbugs.gnu.org
Subject: bug#15122: 24.3.50; [PATCH] byte-compiler warnings about destructive functions
Date: Tue, 20 Aug 2013 10:39:54 -0400	[thread overview]
Message-ID: <jwv1u5opgwm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <788e435c-ad81-40b1-8f92-3a55d3da6cd9@default> (Drew Adams's message of "Tue, 20 Aug 2013 07:07:36 -0700 (PDT)")

>> > might not be aware of when they might be doing so.  I mentioned Scheme's
>> > explicit choice to name all such functions in a noticeable way.  Drawing
>> > attention to (all) use of destructive operations is not necessarily a
>> > useless thing, depending on the user and context.
>> Yes, I like Scheme's convention.
> Then consider adding (subtle, optional) font-lock highlighting of such.
> That would anyway be better than compiler warnings.  The list of fns
> I came up with is a start.  You might even consider putting a recognizable
> property on the function symbols, as well.

Font-lock might be a good idea, indeed.
We could also additionally start to introduce Scheme-style names, like
sort!, reverse!, butlast!, ...


        Stefan





  reply	other threads:[~2013-08-20 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18  5:26 bug#15122: 24.3.50; [PATCH] byte-compiler warnings about destructive functions Drew Adams
2013-08-18 18:38 ` Richard Stallman
2013-08-19  2:59 ` Stefan Monnier
2013-08-19  5:07   ` Drew Adams
2013-08-20  5:07     ` Stefan Monnier
2013-08-20 14:07       ` Drew Adams
2013-08-20 14:39         ` Stefan Monnier [this message]
2013-08-20 15:15           ` Drew Adams
2013-08-21  1:00           ` Leo Liu
2013-08-21  4:24             ` Stefan Monnier
2013-08-21 16:54               ` 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

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

  git send-email \
    --in-reply-to=jwv1u5opgwm.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=15122@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.