unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, John Yates <john@yates-sheets.org>
Subject: Re: Type-error in C code
Date: Fri, 12 Nov 2010 17:47:01 +0100	[thread overview]
Message-ID: <m3r5eqa3qy.fsf@linux-m68k.org> (raw)
In-Reply-To: <83lj4yecnz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Nov 2010 18:20:48 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 12 Nov 2010 11:06:26 -0500
>> From: John Yates <john@yates-sheets.org>
>> 
>> On Fri, Nov 12, 2010 at 10:58 AM, Julien Danjou <julien@danjou.info> wrote:
>> 
>> > OTOH, x_fill_property_data deals with floats too, so using a float here
>> > sounds like a good solution, as you suggested.
>> 
>> Alternatively you could check the atom's value and so long as it is in
>> range you could generate an elisp integer, falling back to a float
>> only when the atom is too large.
>
> That's what I meant, actually (we already do such things in other
> places in Emacs sources).

See make_fixnum_or_float.

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."



  reply	other threads:[~2010-11-12 16:47 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 [this message]
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
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=m3r5eqa3qy.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=john@yates-sheets.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 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).