From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: 'Compiler' functionality for Emacs Lisp
Date: Thu, 29 Jul 2010 11:54:23 +0200 [thread overview]
Message-ID: <jwvr5imehqg.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 87hbjjgdbd.fsf@decebal.nl
> When using for example C++ the compiler does a lot of checks for you.
> For example it checks if all your variables are declared or used and
> it does even find potential memory leaks. Is there something like this
> for Emacs Lisp? I am writing bigger functions nowadays. Yesterday I
> found out that not all my variables where declared in a let block and
> I had forgotten to remove a few I where not using anymore. Is there
> something that could do these checks for me?
The byte-compiler's warnings are pretty much the "best" there
is currently.
Stefan
next prev parent reply other threads:[~2010-07-29 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 3:46 'Compiler' functionality for Emacs Lisp Cecil Westerhof
2010-07-29 4:47 ` Fren Zeee
2010-07-29 7:55 ` Pascal J. Bourguignon
2010-07-29 9:54 ` Stefan Monnier [this message]
2010-07-29 11:47 ` Elena
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=jwvr5imehqg.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.
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).