unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 31852@debbugs.gnu.org
Subject: bug#31852: Make memory-limit obsolete
Date: Sat, 16 Jun 2018 18:02:03 +0300	[thread overview]
Message-ID: <83o9gazses.fsf@gnu.org> (raw)
In-Reply-To: <36f43145-ab73-d6e4-ae70-4d801bfe7583@cs.ucla.edu> (message from Paul Eggert on Sat, 16 Jun 2018 06:38:55 -0700)

> Cc: 31852@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 16 Jun 2018 06:38:55 -0700
> 
> Eli Zaretskii wrote:
> > I don't understand what we gain by declaring
> > this tiny function obsolete
> 
> Nobody uses the function (clearly, since it doesn't work) so we gain simplicity, 
> which is a win.

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

> > Wouldn't it be enough just to add to the function's
> > documentation a note that the estimation should be expected to be
> > inaccurate with modern memory-management technologies?
> 
> Complicating the documentation would work against the goal of
> simplicity.

Then let's just move this to Lisp, and do nothing else.  That's even
simpler, IMO.





  reply	other threads:[~2018-06-16 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16  1:33 bug#31852: Make memory-limit obsolete Paul Eggert
2018-06-16  6:31 ` Eli Zaretskii
2018-06-16 13:38   ` Paul Eggert
2018-06-16 15:02     ` Eli Zaretskii [this message]
2018-06-16 15:34       ` Paul Eggert
2018-06-16 15:51         ` Daniel Colascione
2018-06-16 16:27           ` Paul Eggert

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=83o9gazses.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31852@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).