From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Byte-compiler warnings
Date: Wed, 24 Jun 2015 23:19:48 -0400 [thread overview]
Message-ID: <jwvd20kv624.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 87bng5qrcp.fsf@kuiper.lan.informatimago.com
>> Are there other tools that assist in writing good Elisp code? I know
>> about checkdoc, is there anything else?
> Once upon a time, there was a lot of such tools to help writing lisp
> code, including code pattern matcher, expert systems, AI user models,
> etc.
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, ...).
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.
Stefan
next prev parent reply other threads:[~2015-06-25 3:19 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 [this message]
2015-06-25 3:42 ` Emanuel Berg
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=jwvd20kv624.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.