From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Sun, 20 Mar 2016 18:34:05 +0100 [thread overview]
Message-ID: <87k2kxuk8i.fsf@linux-m68k.org> (raw)
In-Reply-To: <83fuvl6p97.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Mar 2016 19:19:32 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Today I found that some inline functions defined in lisp.h are not in
> src/TAGS. For example, lispstpcpy is not there. After some digging,
> it turned out that lines like the one below confuse etags:
>
> 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?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-03-20 17:34 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 [this message]
2016-03-20 17:59 ` Eli Zaretskii
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
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=87k2kxuk8i.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).