From: "Shigeru Fukaya" <shigeru.fukaya@gmail.com>
To: "Chong Yidong" <cyd@stupidchicken.com>
Cc: 1334@emacsbugs.donarmstrong.com
Subject: bug#1334: 23.0.60; bug of bytecomp arithmetic operations
Date: Sat, 15 Nov 2008 13:04:34 +0900 [thread overview]
Message-ID: <E568E3BAC25C4B158F73E19EE3480F50@LX1> (raw)
In-Reply-To: <874p29kioa.fsf@cyd.mit.edu>
Hi, Chong,
I agree it's too aggressive. I'd just sought for the best.
> Could you separate out the byte-optimize-*-functions part of the patch?
They are mutually affected. So I'll make and send a patch of
byte-opt.el that includes minimal changes to the latest CVS. It is
necessary because the current byte-opt.el still has problems I
pointed. It will take a few days.
Is it ok?
Regards,
Shigeru
----- Original Message -----
From: "Chong Yidong" <cyd@stupidchicken.com>
To: "Shigeru Fukaya" <shigeru.fukaya@gmail.com>
Cc: <1334@emacsbugs.donarmstrong.com>
Sent: Saturday, November 15, 2008 8:10 AM
Subject: Re: 23.0.60; bug of bytecomp arithmetic operations
> Hi Shigeru,
>
> I've been looking through your changes to byte-opt.el. They look good,
> but some of the changes are a little too agressive for my tastes, so
> close to pretest.
>
> Could you separate out the byte-optimize-*-functions part of the patch?
> A mistake in any of these lists could lead to some hard-to-track errors.
> If in doubt, let's simply not perform the optimization for now. We can
> apply these changes after the release.
----- Original Message -----
From: "Chong Yidong" <cyd@stupidchicken.com>
To: "Shigeru Fukaya" <shigeru.fukaya@gmail.com>
Cc: <1334@emacsbugs.donarmstrong.com>
Sent: Saturday, November 15, 2008 8:10 AM
Subject: Re: 23.0.60; bug of bytecomp arithmetic operations
> Hi Shigeru,
>
> I've been looking through your changes to byte-opt.el. They look good,
> but some of the changes are a little too agressive for my tastes, so
> close to pretest.
>
> Could you separate out the byte-optimize-*-functions part of the patch?
> A mistake in any of these lists could lead to some hard-to-track errors.
> If in doubt, let's simply not perform the optimization for now. We can
> apply these changes after the release.
next prev parent reply other threads:[~2008-11-15 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:10 bug#1334: 23.0.60; bug of bytecomp arithmetic operations Chong Yidong
2008-11-15 4:04 ` Shigeru Fukaya [this message]
2008-11-15 4:18 ` Chong Yidong
2008-11-19 12:27 ` Shigeru Fukaya
2008-11-21 7:40 ` Chong Yidong
2008-11-21 9:11 ` Shigeru Fukaya
-- strict thread matches above, loose matches on Subject: below --
2008-11-14 18:11 Chong Yidong
2008-11-12 14:58 Shigeru Fukaya
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=E568E3BAC25C4B158F73E19EE3480F50@LX1 \
--to=shigeru.fukaya@gmail.com \
--cc=1334@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/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).