Re: implicit declarations

al davis <[email protected]>
Newsgroups gmane.comp.gnu.gnucap.devel
Message-ID <20200919221709.59c01d95@z>
> On Wed, Sep 16, 2020 at 02:52:51PM +1000, mwaters517 wrote:
> > getting alot (ie. 100's) of warnings like the following :
> > [..]
> > implicit declarations
> > [..]

How did you get those warnings?
I have wished for that feature for years.

> > I tried to dig a little deeper to see if I could suppress this compiler
> > warning but
> > there's no g++ switch to do that as far as I can see.  
> 
> Hi Mike.
> 
On Wed, 16 Sep 2020 08:11:49 +0200
Felix Salfelder <[email protected]> wrote:
> There is a switch to override the language version. On Arch, g++
> probably defaults to c++17, and in c++17 something about default
> constructors has changed. 

ok .. maybe that's it.

> We need to add the "missing"
> declarations, and they should work with either c++. See "constr" branch
> for an attempt.

These are good changes.  It should have been that way all along.


This raises another question.

Starting with C++11, there is an explicit way to specify this ...
using a generated constructor, disabling a constructor.

I think it is time to switch over to the new way, supported
by compilers since c++11, everywhere, and start requiring c++11 or c++14
or later.

Some systems still in common use do not yet support c++17, so I think
c++14 is appropriate now.

Comments?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.