[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Modules: definition of emacs_value
|
From: |
Daniel Colascione |
|
Subject: |
Re: Modules: definition of emacs_value |
|
Date: |
Mon, 29 Feb 2016 15:15:51 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
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. I really don't like making
32-bit callers cope with 64-bit values. If emacs_value is a pointer, we
have complete freedom with respect to runtime behavior. Putting a
Lisp_Object directly in an emacs_value is a false economy.
signature.asc
Description: OpenPGP digital signature