From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs floating point error during dump?
Date: Sun, 13 Jul 2003 19:06:31 -0400 [thread overview]
Message-ID: <200307132306.h6DN6Wpq004158@rum.cs.yale.edu> (raw)
In-Reply-To: ur84vnu8j.fsf@gnu.org
> When talking about code, you rightfully insist on having the correct
> solution, not just "half correct" or "mostly correct".
>
> Why do you settle for half-solutions with the build infrastructure?
While I completely agree that I'd prefer to have full (and auto-generated)
dependencies between .c and .h files in the makefile, the build
infrastructure has many more "incorrect" parts than that and
I doubt we will ever have a "correct" solution. There is always
a tradeoff between convenience and excessive recompilation.
Stefan
PS: examples that I have bumped into over the last few months:
- modifying an elisp macro will not automatically force a rebuild of all
the .el files that make use of it.
- changing from `make' to `make CFLAGS=-DENABLE_CHECKING' does not
force recompilation of the .o files.
- modifying `Makefile.in' will correctly cause rebuilding of `Makefile'
but will fail to reconstruct the targets that the Makefile describes.
- upgrading libc will not automatically cause `configure' to be rerun.
- deinstalling libpng does not automatically cause `configure' to be rerun.
next prev parent reply other threads:[~2003-07-13 23:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 1:09 emacs floating point error during dump? Miles Bader
2003-07-08 1:51 ` Luc Teirlinck
2003-07-08 3:38 ` Simon Josefsson
2003-07-08 13:21 ` Stefan Monnier
2003-07-09 1:33 ` Miles Bader
2003-07-09 13:44 ` Stefan Monnier
2003-07-10 2:17 ` Miles Bader
2003-07-10 11:32 ` Andreas Schwab
2003-07-11 3:50 ` Richard Stallman
2003-07-11 14:27 ` Stefan Monnier
2003-07-10 16:43 ` Richard Stallman
2003-07-11 0:04 ` Miles Bader
2003-07-11 13:42 ` Sam Steingold
2003-07-11 19:55 ` Richard Stallman
2003-07-11 20:27 ` Sam Steingold
2003-07-12 0:11 ` Kim F. Storm
2003-07-13 0:11 ` Richard Stallman
2003-07-13 0:30 ` Sam Steingold
2003-07-13 1:32 ` Miles Bader
2003-07-13 2:40 ` Sam Steingold
2003-07-13 4:45 ` David Kastrup
2003-07-13 17:34 ` Richard Stallman
2003-07-13 17:37 ` David Kastrup
2003-07-13 18:08 ` Sam Steingold
2003-07-13 8:34 ` Miles Bader
2003-07-13 10:35 ` David Kastrup
2003-07-13 15:33 ` Thien-Thi Nguyen
2003-07-13 23:06 ` Stefan Monnier [this message]
2003-07-13 23:58 ` Sam Steingold
2003-07-14 4:22 ` Eli Zaretskii
2003-07-14 23:18 ` Kim F. Storm
2003-07-15 11:02 ` Richard 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=200307132306.h6DN6Wpq004158@rum.cs.yale.edu \
--to=monnier+gnu/emacs@cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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).