unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Julien Danjou" <julien@danjou.info>,
	"Jan Djärv" <jan.h.d@swipnet.se>,
	emacs-devel@gnu.org
Subject: Re: Type-error in C code
Date: Fri, 12 Nov 2010 19:45:57 +0100	[thread overview]
Message-ID: <m24obm8joa.fsf@igel.home> (raw)
In-Reply-To: <jwv4obmodah.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 12 Nov 2010 09:02:10 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> The error is to put an "Atom" into a cons cell: those can only hold
> Lisp_Objects.  The usual compilation flags won't catch the error because
> both types are actually some kind of integer, but if you
> compile --enable-use-lisp-union-type, the C compiler will
> dutyfully burp.

I think we should remove the union Lisp_Object, and instead define a
struct Lisp_Object { EMACS_INT i; } (reusing the macros of the non-union
type), and make that the default Lisp_Object at least during
development.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  parent reply	other threads:[~2010-11-12 18:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 14:02 Type-error in C code Stefan Monnier
2010-11-12 14:21 ` Julien Danjou
2010-11-12 15:12   ` Jan Djärv
2010-11-12 15:22     ` Julien Danjou
2010-11-12 15:28       ` Julien Danjou
2010-11-12 15:32         ` Julien Danjou
2010-11-12 15:48           ` Eli Zaretskii
2010-11-12 15:58             ` Julien Danjou
2010-11-12 16:06               ` John Yates
2010-11-12 16:20                 ` Eli Zaretskii
2010-11-12 16:47                   ` Andreas Schwab
2010-11-12 19:44                 ` Miles Bader
2010-11-12 15:48       ` Eli Zaretskii
2010-11-12 17:13       ` Jan D.
2010-11-12 21:15     ` Thien-Thi Nguyen
2010-11-13 19:19       ` Jan Djärv
2010-11-13 19:52         ` Thien-Thi Nguyen
2010-11-13 22:23           ` Jan Djärv
2010-11-13 20:38         ` Johan Bockgård
2010-11-14 10:21           ` Jan Djärv
2010-11-12 18:45 ` Andreas Schwab [this message]
2010-11-12 21:00   ` Stefan Monnier
2010-11-15 21:11     ` Julien Danjou
2010-11-15 21:19     ` Andreas Schwab
2010-11-16  5:43       ` Stefan Monnier
2010-11-16  7:56         ` Julien Danjou
2010-11-16  9:05           ` Stephen J. Turnbull
2010-11-16  9:28             ` Julien Danjou
2010-11-16 12:11               ` Stephen J. Turnbull
2010-11-16 15:14           ` Stefan Monnier
2010-11-16 15:38             ` Julien Danjou
2010-11-16 17:05               ` Stefan Monnier
2010-11-16  9:36         ` Andreas Schwab
2010-11-13 20:00   ` Julien Danjou
2010-11-15 16:08     ` 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=m24obm8joa.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=julien@danjou.info \
    --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 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).