warning in boost concept

Hi, this is using boost 1.42, I think the same happens in 1.43 Using boost::accumulators generates a compiler warning in boost/concept_check.hpp:335. it seems the Arg member is a reference, but gcc doesnt like that there is no way to initialize it since it is private and the class does not have a constructor. this is particularly annoying since due to metaprogramming and the lag of variadic templates the instantiation trace in the error message for a single error is a few pages long, and it comes each time I instantiate an accumulator. is there a way to avoid this? Best Daniel

oberhoff wrote:
Hi,
this is using boost 1.42, I think the same happens in 1.43
Using boost::accumulators generates a compiler warning in boost/concept_check.hpp:335. it seems the Arg member is a reference, but gcc doesnt like that there is no way to initialize it since it is private and the class does not have a constructor. this is particularly annoying since due to metaprogramming and the lag of variadic templates the instantiation trace in the error message for a single error is a few pages long, and it comes each time I instantiate an accumulator. is there a way to avoid this? Well, if Arg is *always* a reference, it should be declared in the BOOST_CONEPT_USAGE function.
-- ___________________________________________ Joel Falcou - Assistant Professor PARALL Team - LRI - Universite Paris Sud XI Tel : (+33)1 69 15 66 35

oberhoff wrote:
Hi,
this is using boost 1.42, I think the same happens in 1.43
Using boost::accumulators generates a compiler warning in boost/concept_check.hpp:335. it seems the Arg member is a reference, but gcc doesnt like that there is no way to initialize it since it is private and the class does not have a constructor. this is particularly annoying since due to metaprogramming and the lag of variadic templates the instantiation trace in the error message for a single error is a few pages long, and it comes each time I instantiate an accumulator. is there a way to avoid this?
Declaring a constructor without defining it would fix the issue.

On 2010-04-08 14:52:48 +0200, Mathias Gaunard
oberhoff wrote:
Hi,
this is using boost 1.42, I think the same happens in 1.43
Using boost::accumulators generates a compiler warning in boost/concept_check.hpp:335. it seems the Arg member is a reference, but gcc doesnt like that there is no way to initialize it since it is private and the class does not have a constructor. this is particularly annoying since due to metaprogramming and the lag of variadic templates the instantiation trace in the error message for a single error is a few pages long, and it comes each time I instantiate an accumulator. is there a way to avoid this?
Declaring a constructor without defining it would fix the issue.
so should I forward this to the maintainer of accumulators?

oberhoff wrote:
On 2010-04-08 14:52:48 +0200, Mathias Gaunard
said: oberhoff wrote:
Hi,
this is using boost 1.42, I think the same happens in 1.43
Using boost::accumulators generates a compiler warning in boost/concept_check.hpp:335. it seems the Arg member is a reference, but gcc doesnt like that there is no way to initialize it since it is private and the class does not have a constructor. this is particularly annoying since due to metaprogramming and the lag of variadic templates the instantiation trace in the error message for a single error is a few pages long, and it comes each time I instantiate an accumulator. is there a way to avoid this?
Declaring a constructor without defining it would fix the issue.
so should I forward this to the maintainer of accumulators?
I don't know whether that's accumulators or concept check's fault. File a ticket for accumulators for the time being?

Hi ! Am Freitag, 9. April 2010 15:24:43 schrieben Sie:
oberhoff wrote:
On 2010-04-08 14:52:48 +0200, Mathias Gaunard
Declaring a constructor without defining it would fix the issue.
so should I forward this to the maintainer of accumulators?
I don't know whether that's accumulators or concept check's fault. File a ticket for accumulators for the time being?
I've checked in the proposed check declaring a dummy constructor for gcc-4.x on trunk and release over the weekend. Tests are green (well, we have only one gcc-3.x tester at the moment) and the warning is gone. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold@ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !
participants (4)
-
joel falcou
-
Jürgen Hunold
-
Mathias Gaunard
-
oberhoff