From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Sun, 20 Mar 2016 19:59:28 +0200 [thread overview]
Message-ID: <83a8lt6nen.fsf@gnu.org> (raw)
In-Reply-To: <87k2kxuk8i.fsf@linux-m68k.org> (message from Andreas Schwab on Sun, 20 Mar 2016 18:34:05 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 20 Mar 2016 18:34:05 +0100
>
> > extern _Noreturn void emacs_abort (void) NO_INLINE;
> >
> > Specifically, the very next inline function doesn't wind up in TAGS.
> > The problem is that NO_INLINE part after the argument list. These
> > macros expand either to __attribute__((SOMETHING)) or to nothing;
> > etags knows about __attribute__, but it cannot know about the macros
> > we use for that. The problem happens with any attribute we hide
> > behind a macro, not just with NO_INLINE.
>
> Can't etags reset its parser state after a toplevel semicolon?
No, evidently because it wants to support K&R function definition:
void foo () int arg; { bar = arg; }
That's why, whenever it finds lines like the one above, it resets its
state only after the closing brace.
Hmm... can a function definition use mixed K&R and ANSI style, i.e.
some arguments declared inside the parentheses and some outside, like
this:
void foo (int arg1) int arg2; { bar = baz; }
Or is this invalid C? If so, perhaps we could take note of nonempty
argument list.
next prev parent reply other threads:[~2016-03-20 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 17:19 Help etags parse lisp.j Eli Zaretskii
2016-03-20 17:34 ` Andreas Schwab
2016-03-20 17:59 ` Eli Zaretskii [this message]
2016-03-20 18:11 ` Help etags parse lisp.h Eli Zaretskii
2016-03-21 7:54 ` Help etags parse lisp.j Paul Eggert
2016-03-21 10:58 ` Andreas Schwab
2016-03-21 16:10 ` Eli Zaretskii
2016-03-22 12:46 ` Stefan Monnier
2016-03-22 16:24 ` Eli Zaretskii
2016-03-21 13:40 ` Stefan Monnier
2016-03-21 16:22 ` Eli Zaretskii
2016-03-21 17:40 ` Paul Eggert
2016-03-21 18:13 ` Eli Zaretskii
2016-03-21 21:28 ` John Wiegley
2016-03-22 12:25 ` Stefan Monnier
2016-03-21 18:10 ` Stefan Monnier
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=83a8lt6nen.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.