public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: NightStrike <nightstrike@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: g++ with VLA
Date: Sat, 30 Mar 2024 09:05:23 +0000	[thread overview]
Message-ID: <CAH6eHdTtjRM6iT0yzyZd5-aazGjh=s7+7z93wmiD79e-M1k3fA@mail.gmail.com> (raw)
In-Reply-To: <CAF1jjLspQ39Xu0tpKsFkxyFvgv72aqeUjZ8gVh5WBNaAPVnORw@mail.gmail.com>

On Sat, 30 Mar 2024 at 06:12, NightStrike via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html
>
> That doc states that VLAs are supported in C++ as an extension.
> Compiling the following:
>
> void f(int a, int b[a]);
> void f() {
>   int c[2];
>   f(2, c);
> }
>
> with g++ -std=gnu++20 results in the error: "use of parameter outside
> function body before ']' token".  The docs say nothing about partial
> support of VLA, just that they can be used.

I don't think GNU C++ has any changes to the function declarator
syntax to support variably modified types. You can define a VLA
object, but you can't use earlier function parameters later in the
function-parameter-list, and you can't use int b[*] in a parameter
either.


>
> Where this is useful as an extension is in the somewhat reasonable
> case of including a C header in a C++ program.  If that C header
> declares a function using a C99 VLA, it would be awesome if g++ were
> to accept it in -std=gnu++ mode (and it would be fine if it were
> rejected in -std=c++ mode).  Consider a situation where you cannot
> modify the header, and so have to use it as-is.
>
> Is there perhaps another option to achieve the intended behavior?
>
> If it's not possible, can this be added?
>
> If the consensus is that it shouldn't be added, could the docs at
> least clarify what is supported and what is not in C++?

  reply	other threads:[~2024-03-30  9:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30  6:10 NightStrike
2024-03-30  9:05 ` Jonathan Wakely [this message]
2024-03-30 18:39   ` NightStrike
2024-03-30 18:46     ` NightStrike

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='CAH6eHdTtjRM6iT0yzyZd5-aazGjh=s7+7z93wmiD79e-M1k3fA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=nightstrike@gmail.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.
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).