unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: mast@lysator.liu.se, romain@orebokech.com, emacs-devel@gnu.org,
	bug-cc-mode@gnu.org, acm@muc.de, henrik.enberg@telia.com
Subject: Re: Release of CC Mode 5.31
Date: Thu, 08 Dec 2005 00:41:28 +0200	[thread overview]
Message-ID: <ubqzslecn.fsf@gnu.org> (raw)
In-Reply-To: <jwvacfck7xp.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 07 Dec 2005 14:51:22 -0500)

> Cc: rms@gnu.org, mast@lysator.liu.se, romain@orebokech.com,
> 	emacs-devel@gnu.org, bug-cc-mode@gnu.org, henrik.enberg@telia.com,
> 	acm@muc.de
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 07 Dec 2005 14:51:22 -0500
> 
> > I thought about some Make magic, like making some of the *.elc files
> > dependent on some other *.elc files which need to be compiled first.
> > (We already have COMPILE_FIRST files that work around similar
> > problems.)  Is there any reason why this wouldn't work?
> 
> That would work.  It'd be even better to generate this dependency info
> automatically.  Ideally, the byte-compiler would keep track of which macros
> are used, so that it can automatically generate exact
> dependency information.

WIBNI we had something like "gcc -MM"?

> Note that e.g. if we change the dolist macro, it's not enough to recompile
> subr.el before the other files, since we also need to redump the executable
> after recompiling subr.el.

Well, yeah, I know that there are hard cases where even Make will be
unable to help.  But I think there's a lot to be done before we get
there.

  reply	other threads:[~2005-12-07 22:41 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 12:20 Release of CC Mode 5.31 Alan Mackenzie
2005-12-02 17:15 ` Henrik Enberg
2005-12-02 20:42   ` Alan Mackenzie
2005-12-03 15:58     ` Richard M. Stallman
2005-12-03 16:15       ` Alan Mackenzie
2005-12-03 11:48   ` Alan Mackenzie
2005-12-03 12:40     ` Romain Francoise
2005-12-03 15:33     ` Henrik Enberg
2005-12-04  3:08     ` Richard M. Stallman
2005-12-05 16:48       ` Alan Mackenzie
2005-12-06 16:43         ` Richard M. Stallman
2005-12-04 19:40     ` Eli Zaretskii
2005-12-04 19:45       ` Romain Francoise
2005-12-06 12:11       ` Alan Mackenzie
2005-12-06 20:33         ` Eli Zaretskii
2005-12-07 17:07           ` Richard M. Stallman
2005-12-07 18:14             ` Alan Mackenzie
2005-12-08  4:53               ` Richard M. Stallman
2005-12-07 18:48             ` Eli Zaretskii
2005-12-07 19:51               ` Stefan Monnier
2005-12-07 22:41                 ` Eli Zaretskii [this message]
2005-12-08  4:54                 ` Richard M. Stallman
2005-12-08  4:53               ` Richard M. Stallman
2005-12-08 16:43                 ` Stefan Monnier
2005-12-08 19:47                   ` Eli Zaretskii
2005-12-08 22:24                     ` Stefan Monnier
2005-12-08 23:04                       ` Kim F. Storm
2005-12-08 23:46                         ` Stefan Monnier
2005-12-09 12:30                           ` Eli Zaretskii
2005-12-09 14:42                             ` Stefan Monnier
2005-12-10  4:13                               ` Richard M. Stallman
2005-12-09 12:35                       ` Eli Zaretskii
2005-12-09 14:42                         ` Stefan Monnier
2005-12-09 15:02                       ` Richard M. Stallman
2005-12-08 23:32                   ` Andreas Schwab
2005-12-09  1:42                   ` Richard M. Stallman
2005-12-08 19:29                 ` Eli Zaretskii
2005-12-09  1:43                   ` Richard M. Stallman
2005-12-06 10:32 ` Romain Francoise
2005-12-06 13:09   ` Alan Mackenzie
2005-12-06 13:46   ` Masatake YAMATO
2005-12-06 20:34   ` Eli Zaretskii
2005-12-06 20:49     ` Romain Francoise
2005-12-06 21:04       ` 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=ubqzslecn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=henrik.enberg@telia.com \
    --cc=mast@lysator.liu.se \
    --cc=romain@orebokech.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).