From: Noam Postavsky <npostavs@gmail.com>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 35768@debbugs.gnu.org
Subject: bug#35768: 27.0.50; CC-Mode problems with function definitions with macro names
Date: Thu, 16 May 2019 19:42:55 -0400 [thread overview]
Message-ID: <87k1eqdkzk.fsf@gmail.com> (raw)
In-Reply-To: <CABczVwdjPATqrnw2SmDkO8vmy7pRGom+LeW3XDZa+QR0dAH5bA@mail.gmail.com> (Mauro Aranda's message of "Thu, 16 May 2019 19:19:09 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> I noticed CC-Mode sometimes doesn't identify correctly function names
> when a macro name is involved in the function definition. Try the
> following recipe to see the problem:
>
> 1) emacs -Q
> 2) C-x C-f test.c
> 3) Type the following function definitions:
>
> int DUMMY
> foo (void)
> {
> return 1;
> }
>
> DUMMY int
> bar (void)
> {
> return 0;
> }
>
> 4) Observe that:
> a) foo doesn't get fontified with font-lock-function-name-face, but
> DUMMY does. Consequently, C-c C-z inside foo echoes
> DUMMY as the function name, in the echo area.
> b) In bar, DUMMY gets font-lock-type-face, which I don't
> think is correct. bar gets font-lock-function-name-face and C-c C-z
> works as expected.
>
> ---
>
> Other problem is with fontification of the return type in the following:
>
> bool DUMMY
> baz_t (void)
> {
> return true;
> }
>
> bool
> baz_f (void)
> {
> return false;
> }
>
> Observe that bool doesn't get fontified in baz_t, but DUMMY does. When
> DUMMY is not present, bool gets fontified correctly (as in baz_f).
>
>
> If it helps, I found the problem in a source file with functions that
> have macros that declare some function attributes, like
> _GL_ATTRIBUTE_PURE.
Have you tried customizing c-noise-macro-names, as described in (ccmode) Noise Macros?
next prev parent reply other threads:[~2019-05-16 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 22:19 bug#35768: 27.0.50; CC-Mode problems with function definitions with macro names Mauro Aranda
2019-05-16 23:42 ` Noam Postavsky [this message]
2019-05-17 12:40 ` Mauro Aranda
2019-05-18 12:56 ` Alan Mackenzie
[not found] ` <20190518125628.GA6231@ACM>
2019-05-18 13:56 ` Mauro Aranda
[not found] ` <CABczVwcqmJZRhJDe8wzQxpM4Y52T6AtWKop1ESUmPiycHizasw@mail.gmail.com>
2019-05-18 15:27 ` 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=87k1eqdkzk.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35768@debbugs.gnu.org \
--cc=maurooaranda@gmail.com \
/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.