[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: narrowing considered harmful
From: |
Stefan Monnier |
Subject: |
Re: narrowing considered harmful |
Date: |
Mon, 17 Jun 2013 10:56:07 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
>> 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
- Re: putting double quotes efficiently, (continued)
- Re: putting double quotes efficiently, Andreas Röhler, 2013/06/03
- Message not available
- narrowing considered harmful (was: putting double quotes efficiently), Stefan Monnier, 2013/06/13
- Re: narrowing considered harmful, Leo Liu, 2013/06/13
- Re: narrowing considered harmful, Stefan Monnier, 2013/06/14
- Re: narrowing considered harmful, Leo Liu, 2013/06/14
- Re: narrowing considered harmful, Stefan Monnier, 2013/06/14
- Re: narrowing considered harmful, Leo Liu, 2013/06/16
- Re: narrowing considered harmful,
Stefan Monnier <=
- RE: narrowing considered harmful, Drew Adams, 2013/06/17
- Re: narrowing considered harmful, Stefan Monnier, 2013/06/17
Re: putting double quotes efficiently, Udyant Wig, 2013/06/03
Re: putting double quotes efficiently, Joost Kremers, 2013/06/03