From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: indenting java code
Date: Thu, 06 Nov 2003 22:14:16 GMT [thread overview]
Message-ID: <jwv65hxcfnq.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: mailman.3280.1068074352.21628.help-gnu-emacs@gnu.org
>> `set' is very bad style here.
> Out of curiosity, can you explain why setq is better then set?
- You can't make `set' lexically scoped.
- You can't (in general) analyse `set' to see if the variable was properly
declared, etc... so the byte-compiler can't make sanity checks
or optimizations.
- Basically `set' is in the same category as `eval' which is also
something to keep the few cases where nothing else works.
Stefan
prev parent reply other threads:[~2003-11-06 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 23:47 indenting java code Lowell Kirsh
2003-11-04 0:10 ` Andrew Taylor
2003-11-04 2:09 ` Lowell Kirsh
2003-11-04 15:49 ` Stefan Monnier
2003-11-05 23:17 ` Dan Anderson
[not found] ` <mailman.3280.1068074352.21628.help-gnu-emacs@gnu.org>
2003-11-06 18:12 ` Kevin Rodgers
2003-11-06 22:14 ` Stefan Monnier [this message]
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=jwv65hxcfnq.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
/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).