From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Philipp Stephani Newsgroups: gmane.emacs.devel Subject: Modules: definition of emacs_value Date: Mon, 29 Feb 2016 23:03:25 +0000 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b5d458491024a052cf0a8dd X-Trace: ger.gmane.org 1456787036 13691 80.91.229.3 (29 Feb 2016 23:03:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Feb 2016 23:03:56 +0000 (UTC) To: Emacs developers , Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 01 00:03:51 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aaWr0-0008ES-Uh for ged-emacs-devel@m.gmane.org; Tue, 01 Mar 2016 00:03:51 +0100 Original-Received: from localhost ([::1]:39552 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaWr0-00030q-F4 for ged-emacs-devel@m.gmane.org; Mon, 29 Feb 2016 18:03:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40065) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaWqn-00030Z-P1 for emacs-devel@gnu.org; Mon, 29 Feb 2016 18:03:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aaWqn-0001Xv-22 for emacs-devel@gnu.org; Mon, 29 Feb 2016 18:03:37 -0500 Original-Received: from mail-wm0-x22d.google.com ([2a00:1450:400c:c09::22d]:37764) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aaWqm-0001Xp-NK for emacs-devel@gnu.org; Mon, 29 Feb 2016 18:03:36 -0500 Original-Received: by mail-wm0-x22d.google.com with SMTP id p65so10358359wmp.0 for ; Mon, 29 Feb 2016 15:03:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=N6xnYh8L1HwwH+j/fh8dqBKZbv5EumvzK42Do39EbU4=; b=U607zX9EjShDLvZjRGO/jnum800WFQxScHQRsPsN+N71VX9vPFrQ/e4dmRlfeYWe2p S5nBblFVFtOI0KwJuydCsmhiS0isNG0X/QcQ3XVvBpwyn5o5hfvnKvN5eUnTU5F18R5N V9TGscHvsQ2T7xz8ubEqqEP52FnQ8sIIu392jtaFtKMdTEILiLFNjwNmNnK9XGOwRoaC acpg4HpXnFLUtumpCG8TW62Q8QZN8Z7/VUv8zRNh+SMhQs/fn0Gj5GQ8mzib/ic16VHW a1KXXbP6o86xjs1A54XLzI3ir0Yx7oyAzxHHpryR/YCwH/1Ozcq2+yaEWnhawca8ZoCq rJKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=N6xnYh8L1HwwH+j/fh8dqBKZbv5EumvzK42Do39EbU4=; b=MTNvLJFJHeF0JVU6cxpv+ZNuTQb1qVTcNelYC3CuLUSsiaPIC85jsWg8rXovnUMkg7 1Qi5nPPCGcgdIKgOxx5Raff/q/MY3vJ1lrrvJJ6zW6OMXgpOR6asC59hzR2Rkulqs1Gp BDeA1xXdk9mOaaQd346xhgbYNenPs/QEAIRX5wafk3Ji3kAOMv+VFoABItici/IwCc/s 3Hb9T03L74GsIOY0U716v8/3Zg49sPpvBoIcQTJ/6nJkoMBCtIY22pTvC4K6+vzj6Coc 5MJ9xlzEBg6mAJxrDB1oU3Vk1BXj+bqkAx9OXNrcSOnlDrIvGDIbTkayeycZpFb3GuKa MxLg== X-Gm-Message-State: AD7BkJJe3D4mMJvaZ11lcCguy9U/0NoS0a5KMUWwLzKZ2cfp5axFrZbZwPguoxfBZjdiciG8BlKURhACK0Curw== X-Received: by 10.194.7.201 with SMTP id l9mr6686965wja.16.1456787015400; Mon, 29 Feb 2016 15:03:35 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200831 Archived-At: --047d7b5d458491024a052cf0a8dd Content-Type: text/plain; charset=UTF-8 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? --047d7b5d458491024a052cf0a8dd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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?
--047d7b5d458491024a052cf0a8dd--