unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Why there is no char type?
Date: Wed, 15 Dec 2010 09:03:12 +0100	[thread overview]
Message-ID: <87bp4nbgzj.fsf@lola.goethe.zz> (raw)
In-Reply-To: 87ei9jr5kf.fsf@uwakimon.sk.tsukuba.ac.jp

"Stephen J. Turnbull" <stephen@xemacs.org> writes:

> David Kastrup writes:
>  > "Stephen J. Turnbull" <stephen@xemacs.org> writes:
>  > 
>  > > Leo writes:
>  > >
>  > >  > As the subject line suggested.
>  > >
>  > > You're using the wrong 'macs, that's why.
>  > 
>  > The right one, you mean.
>
> Not if he wants a char type in Lisp.

He asked why there wasn't one.  If he unconditionally wanted one without
wanting to hear reasons, he supposedly would have said so (likely
including asking where to get a different Emacs).

> Both XEmacs and SXEmacs have such a type, and it far more frequently
> leads to detection of bugs than it causes incompatibilities with code
> written for Emacs.

I have a hard time imagining that since automatic conversions in both
directions are in place for compatibility IIRC.  Could you point to a
few instances of these frequently detected bugs from your bug tracker?

-- 
David Kastrup




  reply	other threads:[~2010-12-15  8:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 13:04 Why there is no char type? Leo
2010-12-14 13:57 ` Stephen J. Turnbull
2010-12-14 14:12   ` Eli Zaretskii
2010-12-15  4:55     ` Stephen J. Turnbull
2010-12-15  6:48       ` Eli Zaretskii
2010-12-14 14:31   ` David Kastrup
2010-12-15  5:03     ` Stephen J. Turnbull
2010-12-15  8:03       ` David Kastrup [this message]
2010-12-16 20:20         ` Stephen J. Turnbull
2010-12-16 21:06           ` David Kastrup
2010-12-16 21:44             ` Stephen J. Turnbull
2010-12-15 10:24       ` Leo
2010-12-15 18:40         ` Richard Stallman
2010-12-15 21:19           ` Andy Wingo
2010-12-14 14:11 ` Eli Zaretskii
2010-12-14 14:53   ` Leo
2010-12-14 16:02     ` alin soare
2010-12-14 16:05       ` David Kastrup
2010-12-17  3:39 ` 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=87bp4nbgzj.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).