unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: 59435@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, casouri@gmail.com
Subject: bug#59435: 29.0.50; tree-sitter fails to fontify or indent simple function
Date: Wed, 07 Dec 2022 09:02:23 +0800	[thread overview]
Message-ID: <877cz4m3fk.fsf@yahoo.com> (raw)
In-Reply-To: <87bkog5jgh.fsf@oldenburg.str.redhat.com> (Florian Weimer's message of "Tue, 06 Dec 2022 22:08:14 +0100")

Florian Weimer <fweimer@redhat.com> writes:

> Some clarification:
>
> Implicit ints were removed from the language in 1999.  GCC 14 (to be
> released in 2024) will likely no longer accept them by default, along
> with implicit function declarations (also removed in 1999).  But you can
> still get them back using -std=gnu89, and there are no plans to remove
> that.

What about -std=gnu99? Is there a way to get them back there?

> Old-style function definitions will finally be removed in C2X (which
> will probably be called C23), but I've been told that it will be several
> years (but probably not anything close to 25) until GCC switches to
> -std=gnu23 (or whatever the year will be the year of the standard in the
> end).  Function declarations which are not a prototype—void foo();—will
> change meaning and denote a function with an empty parameter list, same
> as today: foo(void);.

No more:

  int (*pFillSpans) ();

  (*pFillSpans) (pDrawable, pGc, nInit, pptInit, pwidthInit, fSorted)

?

Will there be an option to get that back in gnu23?

> Old-style function declarations are still in C18, and so are function
> declarations without a prototype.

Thanks.





  reply	other threads:[~2022-12-07  1:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871qpw7s9k.fsf.ref@yahoo.com>
2022-11-21  6:09 ` bug#59435: 29.0.50; tree-sitter fails to fontify or indent simple function Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21  9:45   ` Yuan Fu
2022-11-21 11:57     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 13:53       ` Eli Zaretskii
2022-11-24 23:38         ` Richard Stallman
2022-11-25  5:12           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-28 21:37             ` Richard Stallman
2022-11-29  0:46               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 23:12                 ` Richard Stallman
2022-12-05  1:15                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-25  6:38           ` Yuan Fu
2022-11-25  7:45           ` Eli Zaretskii
2022-11-28 21:37             ` Richard Stallman
2022-12-06 21:08         ` Florian Weimer
2022-12-07  1:02           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-07 10:50             ` Florian Weimer
2022-12-07 11:01               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-21 13:52     ` Stefan Kangas
2022-11-23 23:31   ` Yuan Fu

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=877cz4m3fk.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59435@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=fweimer@redhat.com \
    --cc=luangruo@yahoo.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 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).