From: Daniel Colascione <dancol@dancol.org>
To: Philipp Stephani <p.stephani2@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Modules: definition of emacs_value
Date: Wed, 2 Mar 2016 12:14:01 -0800 [thread overview]
Message-ID: <56D74989.1070404@dancol.org> (raw)
In-Reply-To: <CAArVCkRferN+rySSQQGEp3XHpCzW+_NJ4FQjpiJJk5gb1w=8xw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 830 bytes --]
On 03/02/2016 10:30 AM, Philipp Stephani wrote:
>
>
> Daniel Colascione <dancol@dancol.org <mailto:dancol@dancol.org>> schrieb
> am Di., 1. März 2016 um 00:15 Uhr:
>
> On 02/29/2016 03:03 PM, Philipp Stephani wrote:
> > Is it a strict requirement that emacs_value be a pointer? If not,
> > couldn't we simply define it as int64 and assume that that will be
> large
> > enough to hold a Lisp_Object for the foreseeable future? Or do we
> expect
> > Lisp_Object to ever grow beyond 64 bits?
>
> I don't like giving users raw Lisp_Objects.
>
>
> But we are already doing that in most cases (64-bit pointers and
> Lisp_Objects): the pointer is not a real pointer, just a Lisp_Object
> cast to a pointer type.
I know, and I don't like it. I wish it were a real pointer.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-02 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 23:03 Modules: definition of emacs_value Philipp Stephani
2016-02-29 23:15 ` Daniel Colascione
2016-03-02 14:37 ` Stefan Monnier
2016-03-02 18:14 ` Philipp Stephani
2016-03-04 1:04 ` Stefan Monnier
2016-03-04 1:24 ` John Wiegley
2016-03-02 18:30 ` Philipp Stephani
2016-03-02 20:14 ` Daniel Colascione [this message]
2016-03-31 17:32 ` Philipp Stephani
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=56D74989.1070404@dancol.org \
--to=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
/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).