all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Mon, 21 Mar 2016 11:58:14 +0100	[thread overview]
Message-ID: <mvm7fgwdrnd.fsf@hawking.suse.de> (raw)
In-Reply-To: <56EFA8B2.90904@cs.ucla.edu> (Paul Eggert's message of "Mon, 21 Mar 2016 00:54:26 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> Eli Zaretskii wrote:
>>> >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; }
>
> OK, how about if it resets its state when it sees a toplevel semicolon not
> immediately followed by "{"?

void foo (a, b) int a; int b; {}

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."



  reply	other threads:[~2016-03-21 10:58 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 [this message]
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=mvm7fgwdrnd.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=eggert@cs.ucla.edu \
    --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 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.