all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Tue, 22 Mar 2016 08:46:59 -0400	[thread overview]
Message-ID: <jwv1t72u1p6.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83y49b6cce.fsf@gnu.org

>   TYPE0 foo (arg1, arg2, arg3, ..., argN)

The first potential difference here is that each arg is
a single identifier.  Of course, in non-K&R declarations, this can also
be the case, but at least if there's a *, a [..], or two identifiers
without a comma between them, then we know already it's not K&R.

> Hmm... can we use the fact that in a K&R definition, the last token
> before the opening brace "{" of the body is always a semicolon?  So if
> there's no semi-colon there, then it's a function that needs to be
> tagged?  (Of course, the semicolon could be hidden behind some clever
> macro, but I think we don't need to cater to such uses.)

Sounds fine, yes,


        Stefan




  reply	other threads:[~2016-03-22 12:46 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
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 [this message]
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=jwv1t72u1p6.fsf-monnier+gmane.emacs.devel@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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.