unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Strange change in bytecmop.el
Date: Fri, 22 Jul 2005 15:43:12 -0400	[thread overview]
Message-ID: <jwvacke4ohn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f7ccd24b05072116127febe89a@mail.gmail.com> (Juanma Barranquero's message of "Fri, 22 Jul 2005 01:12:43 +0200")

> I think the handling in byteopt.el is about generating bytecode (or
> not doing it, for XEmacs-specific code) while the one in bytecomp.el
> is about not issuing warnings for XEmacs features. For example, it
> silences a warning in flymake.el about the use of
> `multiple-value-bind'.

The one in byteopt.el was introduced mostly to remove spurious warnings.
The fact that it optimizes the bytecode was just a nicve side-effect.
So I'm wondering in which circumstance the new code is useful/necessary.


        Stefan

  reply	other threads:[~2005-07-22 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 21:49 Strange change in bytecmop.el Stefan Monnier
2005-07-21 23:12 ` Juanma Barranquero
2005-07-22 19:43   ` Stefan Monnier [this message]
2005-07-22 22:52 ` Richard M. Stallman
2005-07-23 18:45   ` Stefan Monnier
2005-07-24 14:41     ` Richard M. Stallman
2005-07-24 16:44       ` David Kastrup
2005-07-25  1:43         ` Richard M. Stallman
2005-07-25  1:59           ` David Kastrup
2005-07-25 11:39             ` Robert J. Chassell
2005-07-25 12:51               ` David Kastrup
2005-07-25 16:03             ` Richard M. Stallman
2005-07-25 17:21               ` David Kastrup
2005-07-26  8:12             ` Juanma Barranquero
2005-07-26  8:44               ` David Kastrup
2005-07-26 10:09                 ` Juanma Barranquero
2005-07-26 12:38                   ` David Kastrup
2005-07-26 12:58                     ` Juanma Barranquero
2005-07-28 22:04                 ` Kim F. Storm
2005-07-24 14:41     ` Richard M. Stallman

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=jwvacke4ohn.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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).