From: Daniel Colascione <dancol@dancol.org>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Daniel Colascione <dan.colascione@gmail.com>
Cc: 7918@debbugs.gnu.org
Subject: bug#7918: [PATCH] cc-mode: only the first clause of a for-loop should be checked for declarations
Date: Thu, 25 Feb 2016 22:33:06 -0800 [thread overview]
Message-ID: <56CFF1A2.4060506@dancol.org> (raw)
In-Reply-To: <56CFF157.50700@dancol.org>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On 02/25/2016 10:31 PM, Daniel Colascione wrote:
> On 02/25/2016 10:18 PM, Lars Ingebrigtsen wrote:
>> + ;; After a ";" in a for-block. A declaration can never
>> + ;; begin after a `;' if the most enclosing paren is a
>> + ;; `('.-declarators' handles the rest.
>
> Hrm. That's not true in general. Consider Java's try-with-resources
> construct:
>
> try (Foo foo = new Foo(); Bar bar = new Bar()) { ... }
>
Gah, of course that's true in a `for' block specifically.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-26 6:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 6:36 bug#7918: [PATCH] cc-mode: only the first clause of a for-loop should be checked for declarations Daniel Colascione
2016-02-26 6:18 ` Lars Ingebrigtsen
2016-02-26 6:31 ` Daniel Colascione
2016-02-26 6:33 ` Daniel Colascione [this message]
2016-03-01 18:02 ` Alan Mackenzie
2016-03-01 18:05 ` Daniel Colascione
2016-04-01 16:18 ` Alan Mackenzie
2016-04-25 18:04 ` Alan Mackenzie
[not found] ` <handler.7918.D7918.146160769022226.notifdone@debbugs.gnu.org>
2017-06-29 1:06 ` npostavs
2017-07-03 19:09 ` Glenn Morris
2017-07-03 19:46 ` npostavs
2017-07-03 20:18 ` Alan Mackenzie
2017-07-05 15:55 ` Glenn Morris
2017-07-05 20:14 ` Alan Mackenzie
2017-07-06 1:39 ` Glenn Morris
2017-07-07 14:47 ` Alan Mackenzie
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=56CFF1A2.4060506@dancol.org \
--to=dancol@dancol.org \
--cc=7918@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=larsi@gnus.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.