unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: narrowing considered harmful
Date: Mon, 17 Jun 2013 10:56:07 -0400	[thread overview]
Message-ID: <jwvli68rdln.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: m1r4g257nw.fsf@gmail.com

>> I wouldn't worry about it.  It can even be a bad idea (set-marker to
>> nil requires scanning the whole list of markers, so it can take a while.
>> It can be more efficient to let the GC collect them later on).
>> 
>> 
>> Stefan

> Good to know this. The manual contains this:

> ,----[ (info "(elisp)Overview of Markers") ]
> |      ;; When you are finished using a marker, make it point nowhere.
> |      (set-marker m1 nil)
> |           => #<marker in no buffer>
> `----

> Should that be changed?

Not necessarily: whether it's better to nil them explicitly or to leave
them as they are depends on the specific case.


        Stefan




  reply	other threads:[~2013-06-17 14:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  5:43 putting double quotes efficiently C K Kashyap
2013-06-03  7:26 ` Andreas Röhler
2013-06-03  7:55   ` Andreas Röhler
2013-06-03  8:03     ` C K Kashyap
2013-06-03  9:10       ` Andreas Röhler
2013-06-03 11:52         ` C K Kashyap
     [not found]       ` <mailman.918.1370250440.22516.help-gnu-emacs@gnu.org>
2013-06-13 14:40         ` narrowing considered harmful (was: putting double quotes efficiently) Stefan Monnier
2013-06-14  3:54           ` narrowing considered harmful Leo Liu
2013-06-14 13:00             ` Stefan Monnier
2013-06-14 16:51               ` Leo Liu
2013-06-15  2:43                 ` Stefan Monnier
2013-06-16 16:42                   ` Leo Liu
2013-06-17 14:56                     ` Stefan Monnier [this message]
2013-06-17 15:20                       ` Drew Adams
2013-06-17 16:48                         ` 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=jwvli68rdln.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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.
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).