all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>,
	"Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: More over-engineering
Date: Sat, 28 Nov 2015 15:13:26 -0800	[thread overview]
Message-ID: <565A3516.5000001@cs.ucla.edu> (raw)
In-Reply-To: <jwv610ntji7.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
> The only advantage in this respect is that the representation of
> Lisp_Object is encapsulated inside Emacs core, so the same module can be
> used with a "emacs-32bit-narrow-int" and on "emacs-32bit-wide-int".
> The cost for that minor advantage seems way out of proportion.

I agree.  Although I'm a fan of --with-wide-int, I don't think it should force 
this extra complication in modules.  People who want Emacs with wide ints can 
build modules to suit.  This is the same as 32- vs 64-bit off_t, in traditional 
C libraries.



  parent reply	other threads:[~2015-11-28 23:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 17:00 More over-engineering Stefan Monnier
2015-11-27 17:12 ` Aurélien Aptel
2015-11-27 17:37   ` David Kastrup
2015-11-27 18:02   ` Stefan Monnier
2015-11-27 18:19     ` Eli Zaretskii
2015-11-27 18:53       ` Stefan Monnier
2015-11-27 19:32         ` Eli Zaretskii
2015-11-27 21:55           ` Stefan Monnier
2015-11-28  7:51             ` Eli Zaretskii
2015-11-28 16:22               ` Stefan Monnier
2015-11-28 16:34                 ` Eli Zaretskii
2015-11-28 23:13     ` Paul Eggert [this message]
2015-11-30 19:40       ` Stefan Monnier
2015-11-30 20:04         ` Eli Zaretskii
2015-11-30 20:39           ` Stefan Monnier
2015-11-30 20:49             ` Eli Zaretskii
2015-12-06 21:16               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=565A3516.5000001@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.