GNU bug report logs - #31852
Make memory-limit obsolete

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Subject: bug#31852: closed (Re: bug#31852: Make memory-limit obsolete)
Date: Sat, 16 Jun 2018 15:36:03 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#31852: Make memory-limit obsolete

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 31852 <at> debbugs.gnu.org.

-- 
31852: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31852
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 31852-done <at> debbugs.gnu.org
Subject: Re: bug#31852: Make memory-limit obsolete
Date: Sat, 16 Jun 2018 08:34:52 -0700

Eli Zaretskii wrote:

> If nobody uses the function, I see no gain at all, because obsoleting
> a function tells those who use it not to.

If Emacs has useless and confusing features that consume documentation space and 
implementation resources, that is a net harm to current and future users. 
Omitting such features is therefore a net gain to users. The benefit to users by 
omitting useless and confusing features is worth the maintenance cost to us of 
obsoleting these features.

That being said, it appears I haven't convinced you to obsolete memory-limit, so 
I installed patch 1 but not patch 2 and am closing the bug report.

[Message part 3 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Emacs bug reports <bug-gnu-emacs <at> gnu.org>
Subject: Make memory-limit obsolete
Date: Fri, 15 Jun 2018 18:33:47 -0700

[Message part 4 (text/plain, inline)]

Tags: patch

The memory-limit function has an implementation that is a relic of 
long-ago days when the heap was allocated via sbrk. This assumption is 
often no longer true now that ASLR is popular, and once we get portable 
dumping work it'll be true even less often. Since memory-limit returns 
nonsense so often and since nobody cares, we can and should mark 
memory-limit as obsolete. On its way out we can move it to a Lisp 
implementation and cause it to be at least somewhat more plausible.

Proposed patches attached. The first patch moves memory-limit to Lisp, 
the second one marks it obsolete. I didn't know where to put the Lisp 
implementation so I put it into lisp/subr.el.

[0001-Rewrite-memory-limit-in-Lisp.patch (text/x-patch, attachment)]

[0002-Obsolete-memory-limit.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.