From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Nix' <nix@esperi.org.uk>, 'Miles Bader' <miles@gnu.org>,
'Jeremiah Dodds' <jeremiah.dodds@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Better startup error handling
Date: Sat, 28 Apr 2012 15:39:15 -0400 [thread overview]
Message-ID: <jwv397nzm3k.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9D6D1899732043718AD797F833C1439A@us.oracle.com> (Drew Adams's message of "Sat, 28 Apr 2012 08:55:26 -0700")
>> > Downsides: loads the byte-compiler even in sessions that
>> > don't need it, and notably inefficient.
>> Exactly: in theory it's straightforward, but doing it well
>> will require more work. IIRC there are some other issues such as
>> the fact that .emacs code tends to be very different from typical
>> code in Elisp packages, and the kinds of things we want to flag
>> aren't all the same (some things are acceptable/normal/unavoidable
>> in one but not in the other).
> No flames please, but I have a different objection to this idea.
> Perhaps you hinted at in in your last sentence - not sure. Anyhooo...
I largely agree, and that's indeed some of the issues I was hinting at.
Rather than try to detect errors (such as wrong-number of args) which
will/would be detected at run-time anyway, the purpose would be to
detect use of obsolete/deprecated vars/functions/functionality.
But as you mention, such warnings should be kept sufficiently discreet
since a user may elect to keep "old" code if she uses the same .emacs
with various versions/flavors of emacs.
Stefan
next prev parent reply other threads:[~2012-04-28 19:39 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 0:24 proposal to make null string handling more emacs-y Steve Yegge
2012-04-25 4:45 ` Karl Fogel
2012-04-25 6:28 ` Miles Bader
2012-04-25 6:34 ` Miles Bader
2012-04-25 13:21 ` Ted Zlatanov
2012-05-01 22:01 ` Randal L. Schwartz
2012-04-25 7:53 ` Helmut Eller
2012-04-25 8:22 ` Eli Zaretskii
2012-04-25 14:28 ` Stefan Monnier
2012-04-25 14:35 ` Eli Zaretskii
2012-04-25 15:30 ` Stefan Monnier
2012-04-25 16:41 ` Miles Bader
2012-04-25 16:45 ` Andreas Schwab
2012-04-25 16:46 ` Juanma Barranquero
2012-04-26 21:20 ` Steve Yegge
2012-04-26 22:11 ` Miles Bader
2012-04-26 23:52 ` Steve Yegge
2012-04-27 0:29 ` Miles Bader
2012-04-27 3:20 ` Jeremiah Dodds
2012-04-27 3:41 ` Miles Bader
2012-04-27 3:59 ` Jeremiah Dodds
2012-04-27 4:24 ` Miles Bader
2012-04-27 8:49 ` Thien-Thi Nguyen
2012-04-27 14:23 ` Nix
2012-04-28 2:07 ` Better startup error handling (was: proposal to make null string handling more emacs-y) Stefan Monnier
2012-04-28 12:04 ` Better startup error handling Nix
2012-04-28 15:16 ` Stefan Monnier
2012-04-28 15:42 ` David Engster
2012-04-28 15:55 ` Drew Adams
2012-04-28 19:39 ` Stefan Monnier [this message]
2012-04-28 17:26 ` Lars Magne Ingebrigtsen
2012-04-30 8:43 ` Christian Lynbech
2012-04-30 9:18 ` chad
2012-04-27 16:35 ` proposal to make null string handling more emacs-y Richard Stallman
2012-04-27 1:10 ` Stefan Monnier
2012-04-27 1:16 ` Lars Magne Ingebrigtsen
2012-04-27 16:35 ` Richard Stallman
2012-04-28 11:13 ` Eli Barzilay
2012-04-28 17:02 ` Richard Stallman
2012-04-28 19:48 ` Stefan Monnier
2012-04-28 21:56 ` Eli Barzilay
2012-06-03 3:45 ` Richard Stallman
2012-04-27 4:17 ` Steve Yegge
2012-04-27 6:36 ` Eli Zaretskii
2012-04-27 19:05 ` Steve Yegge
2012-04-27 21:24 ` Drew Adams
2012-04-28 4:43 ` Steve Yegge
2012-04-28 6:58 ` Andreas Schwab
2012-04-29 21:26 ` Odd formatting (was: proposal to make null string handling more emacs-y) Lars Magne Ingebrigtsen
2012-04-30 7:48 ` Odd formatting Steinar Bang
2012-04-30 10:14 ` Antoine Levitt
2012-04-30 13:27 ` Nix
2012-04-28 2:02 ` proposal to make null string handling more emacs-y Stefan Monnier
2012-04-25 14:51 ` Lars Magne Ingebrigtsen
2012-04-29 17:00 ` Andreas Röhler
2012-04-29 17:08 ` Drew Adams
2012-04-29 17:29 ` Andreas Röhler
2012-04-29 18:01 ` Drew Adams
2012-04-29 19:51 ` PJ Weisberg
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=jwv397nzm3k.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jeremiah.dodds@gmail.com \
--cc=miles@gnu.org \
--cc=nix@esperi.org.uk \
/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).