unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117941: Default to stack objects on non-GNU/Linux, non-DOS_NT platforms.
Date: Thu, 25 Sep 2014 13:14:57 +0300	[thread overview]
Message-ID: <831tr0vwf2.fsf@gnu.org> (raw)
In-Reply-To: <5423E5B0.4070002@yandex.ru>

> Date: Thu, 25 Sep 2014 13:51:44 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: emacs-devel@gnu.org
> 
> On 09/25/2014 12:15 PM, Eli Zaretskii wrote:
> 
> > It was done in complete silence, without prior discussions wrt
> > whether to make this the default.  (Yes, I suggested that, but no
> > one replied, and we never discussed it.)
> 
> IMO 1) any discussions whether to make USE_STACK_LISP_OBJECTS the default
> makes no sense until we know whether it's worth the complexities at all.
> For the latter, we need a lot of feedback from users, preferably with
> the very different usage patterns and workloads.  The simplest (and the
> only reliable) method is to enable it by default and see what happens.
> OTOH I'm not against making it opt-out, as you suggested.

I suggested, and no one responded.  Ergo, no discussions.

You get more feedback if you enable the feature on all the platforms
that can support it.  Which is exactly my point.

> > It arbitrarily excludes the native MS-Windows builds from this
> > feature, for no good reasons: the 64-bit Windows build has no
> > problems with it
> 
> IMO 2) responsible developer should not enable any code she/he can't
> test.

You elided the part where I said that Paul could have asked others to
add whatever is necessary for 32-bit Windows.

> If you are rather sure that it should work on 64-bit MS-Windows

We tested that, so yes, I'm sure, as should be anyone else who reads
this list.

> > In general, every feature that exists only on some platforms is a
> > Bad Thing, as it introduces maintenance problems and in particular
> > makes people who work on different platforms unable to usefully
> > compare what they see and solve problems reported by others.
> 
> USE_STACK_LISP_OBJECT is not such a feature.  It's rather under
> construction and not yet populated to all (most?) platforms we aim
> to support.  If you want to help with that, you're always welcome.

You asked help for testing on Windows, and I did just that.  If you
need more help, you need but to ask.

> > In sum, I don't understand these sneaky practices, and I wish they'd
> > stopped.
> 
> Sneaky?  I would call it too brave.

Whatever you call it, it's not how we do things here.  Please don't
follow that bad example, and please don't get fascinated by it.



  reply	other threads:[~2014-09-25 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  8:15 [Emacs-diffs] trunk r117941: Default to stack objects on non-GNU/Linux, non-DOS_NT platforms Eli Zaretskii
2014-09-25  9:51 ` Dmitry Antipov
2014-09-25 10:14   ` Eli Zaretskii [this message]
2014-09-25 12:52   ` Stefan Monnier
2014-09-25 16:12     ` Dmitry Antipov
2014-09-25 18:12       ` Stefan Monnier
2014-09-25 19:08         ` Paul Eggert
2014-09-25  9:52 ` Eli Zaretskii
2014-09-25 16:06 ` Paul Eggert
2014-09-25 16:48   ` Eli Zaretskii
2014-09-25 18:46     ` Paul Eggert
2014-09-25 19:16       ` Eli Zaretskii
2014-09-25 20:56         ` 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=831tr0vwf2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@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.
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).