From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Byte-compiler warnings
Date: Thu, 25 Jun 2015 05:42:23 +0200 [thread overview]
Message-ID: <87mvzoh2sg.fsf@nl106-137-147.student.uu.se> (raw)
In-Reply-To: jwvd20kv624.fsf-monnier+gnu.emacs.help@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The tendency over the year has been first to move it
> all into the compiler (since the kind of analysis
> needed to give those warnings is often useful for
> a compiler to generate better code as well), and
> then to add specialized tools again (that focus on
> particular coding errors). IIUC the reason to
> develop the newer tools separately from the
> compilers is because they tend to use different
> analyses (e.g. more superficial (paying attention to
> identifier names), or much more costly, or that
> require extra information/setup from the coders,
> ...).
If it were up to me, superficial or super-costly, it
would still be placed along with the compiler and
invoked with options rather than having that as
separate tools.
> In any case, within the Elisp realm, we're still at
> the stage where the compiler is the most common
> place to add warnings. There are a few other tools
> (elint and checkdoc), of course.
The compiler warnings are great and perhaps more can
be added still? For example, remember the discussion
`if' and (if (not ...)) vs `when' and `unless'? No?
Anyway at that time I thought `if' was better because
then you can add an else clause later (if necessary)
without having to change the function, and you can
start writing the block without thinking how it will
end. I understand that thinking but for whatever
reason somewhere along the way I just started using
when/unless instead and now I think those are much
better whenever there isn't an else path (with
when/unless, `if' also signals there is one).
Perhaps the compiler can warn about that as well? But,
if it gets that aggressive and subjective in, eh,
"style", then people will get crazy if they can't shut
it up if their style conflicts. So I think warnings
should be added in the thousands, and then mutable one
by one...
I'll try elint tomorrow. checkdoc is good, no doubt,
as is the help. Not all functions in official Emacs
(in Gnus, for example) do as checkdoc says and mention
the args in the correct order and all that. It makes
sense and is easy, so why not just do it?
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-06-25 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5561.1435138202.904.help-gnu-emacs@gnu.org>
2015-06-24 11:27 ` Byte-compiler warnings Pascal J. Bourguignon
2015-06-25 1:52 ` Emanuel Berg
2015-06-25 2:30 ` Emanuel Berg
2015-06-25 3:19 ` Stefan Monnier
2015-06-25 3:42 ` Emanuel Berg [this message]
2015-06-24 9:29 Marcin Borkowski
2015-06-24 23:50 ` Emanuel Berg
2015-06-25 12:56 ` Nicolas Richard
[not found] ` <mailman.5606.1435189903.904.help-gnu-emacs@gnu.org>
2015-06-25 3:06 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2010-09-12 18:12 byte-compiler warnings Joost Kremers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvzoh2sg.fsf@nl106-137-147.student.uu.se \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.