[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#59992] [PATCH 1/2] tests: Fix 'type defaults' error in link_cond du
From: |
Frederic Berat |
Subject: |
[bug#59992] [PATCH 1/2] tests: Fix 'type defaults' error in link_cond due to main not being properly declared |
Date: |
Thu, 15 Dec 2022 08:12:35 +0100 |
For the record:
cat > less.c <<'END'
/* Valid C but deliberately invalid C++ */
int main (void)
{
int new = 0;
return new;
}
END
$> g++ less.c
less.c: In function ‘int main()’:
less.c:4:7: error: expected unqualified-id before ‘new’
4 | int new = 0;
| ^~~
less.c:5:13: error: expected type-specifier before ‘;’ token
5 | return new;
| ^
On Tue, Dec 13, 2022 at 7:35 AM Frederic Berat <fberat@redhat.com> wrote:
>
> On Mon, Dec 12, 2022 at 9:15 PM Zack Weinberg <zack@owlfolio.org> wrote:
> >
> > On 2022-12-12 2:05 AM, Frederic Berat wrote:
> > > This is related to an effort to prepare Automake for future GCC/Clang
> > > versions which set c99 as default standard to be used.
> > > Not properly declaring main as "int main(...)" is rejected since c99.
> > ...
> > > /* Valid C but deliberately invalid C++ */
> > > -main ()
> > > +int main (void)
> >
> > Note the comment. Is this test program still invalid C++ after your change?
>
> I assumed yes, since "new" should be a standard symbol, but I actually
> forgot to double check.
>
> >
> > zw
> >
> >
> >
> >
[bug#59993] [PATCH 2/2] tests: Fix implicit function declaration errors, Frederic Berat, 2022/12/12
[bug#59993] [PATCH 2/2] tests: Fix implicit function declaration errors, Frederic Berat, 2022/12/15
[bug#59993] [PATCH 2/2] tests: Fix implicit function declaration errors, Zack Weinberg, 2022/12/28
[bug#59993] [PATCH v2 2/3] tests: Fix implicit function declaration errors, Frederic Berat, 2022/12/16