unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: Intervals crash
Date: Sun, 26 Sep 2010 00:07:10 +0200	[thread overview]
Message-ID: <83vd5tqxyp.fsf@gnu.org> (raw)
In-Reply-To: <87hbhd1wn4.fsf@uwakimon.sk.tsukuba.ac.jp>

> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: cyd@stupidchicken.com,
>     emacs-devel@gnu.org
> Date: Sun, 26 Sep 2010 03:54:55 +0900
> 
> Eli Zaretskii writes:
> 
>  > And what makes you think I need a paternalistic lecture about
>  > demerits of unsigned data types?  You already had your chance once,
>  > and I let it go.  Why do you think I deserve it twice in a row?
> 
> I don't think you deserve it.  I think Emacs deserves the benefit of
> XEmacs's experience, and you were rebutting with bogus claims about
> what Emacs "needs".  It would be a shame if that discourages others
> from improving Emacs, that's all.

How can I "rebut" theoretical arguments that are well known to every
experienced C programmer?  Who would object that in their right mind?
You didn't say anything that would be practically applicable to the
issue at hand.  You are preaching to the choir.

Did you even look at the Emacs sources, wrt to EMACS_UINT usage?  Do
you know how many times it is used?  Or are you talking out of pure
theory?

I posted a specific issue with code fragments, which gave birth to
this thread.  If you can help understand what's going on there, it
will be greatly appreciated.  Otherwise, this conversation goes
nowhere.



  reply	other threads:[~2010-09-25 22:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 18:23 Intervals crash Chong Yidong
2010-09-23 18:52 ` Chong Yidong
2010-09-23 19:01   ` Eli Zaretskii
2010-09-23 19:09     ` Chong Yidong
2010-09-23 19:32       ` Eli Zaretskii
2010-09-23 18:57 ` Eli Zaretskii
2010-09-24  6:12   ` Stephen J. Turnbull
2010-09-24  8:16     ` Eli Zaretskii
2010-09-24  8:52       ` Stephen J. Turnbull
2010-09-24 10:03         ` Eli Zaretskii
2010-09-25 14:34           ` Stephen J. Turnbull
2010-09-25 16:10             ` Eli Zaretskii
2010-09-25 18:54               ` Stephen J. Turnbull
2010-09-25 22:07                 ` Eli Zaretskii [this message]
2010-09-26 13:08                   ` Stephen J. Turnbull
2010-09-26 19:22                     ` Miles Bader
2010-09-26 19:33                       ` David Kastrup
2010-09-27  4:53                       ` Stephen J. Turnbull
2010-09-27  6:55                         ` David Kastrup
2010-09-27  7:42                           ` Jan Djärv
2010-09-27  8:34                             ` Eli Zaretskii
2010-09-27  9:02                               ` David Kastrup
2010-09-27 11:02                                 ` Eli Zaretskii
2010-09-27  8:36                           ` Eli Zaretskii
2010-09-27  8:50                           ` Stephen J. Turnbull
2010-09-27  9:39                             ` David Kastrup
2010-09-27  9:45                               ` Lars Magne Ingebrigtsen
2010-09-27 10:11                               ` Stephen J. Turnbull
2010-09-24 10:31 ` Eli Zaretskii

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=83vd5tqxyp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.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).