Re: g++ extension for Concepts TS

cc Andrew Sutton From: gcc-ow...@gcc.gnu.org on behalf of Christopher Di Bella Sent: April 2, 2017 8:57 AM To: gcc Mailing List Subject: g++ extension for Concepts TS Hey all, I've been working on a concept

RE: Named parameters

Note that a proposal for named arguments was recently presented to the C++ standards committee [1], and they did not seem receptive to it [2]. The proposal was for a different syntax (name : value), but the objections were not related to the syntax. Regards, Nate [1]

RE: [boost] lots of warning with gcc-4.8.1 + boost-1.54.0

On 3 July 2013 02:41, Nathan Ridge wrote: Lots of warnings like this: ./boost/bind/arg.hpp:37:22: warning: typedef ‘T_must_be_placeholder’ locally defined but not used [-Wunused-local-typedefs] when building 1.54.0 with gcc-4.8.1 (fedora f19) This warning is new in GCC 4.8, and I have

PR 50025 (uniform initialization of class member of reference type)

Hi, I'm just wondering, is there any chance of fixing PR 50025 [1] soon? It concerns uniform initialization of a class member of reference type. I have been using GCC to do C++11 development for a while now, and this one bug has been a bit of an eyesore IMO, that has been keeping the uniform out

RE: [boost] lots of warning with gcc-4.8.1 + boost-1.54.0

Lots of warnings like this: ./boost/bind/arg.hpp:37:22: warning: typedef ‘T_must_be_placeholder’ locally defined but not used [-Wunused-local-typedefs] when building 1.54.0 with gcc-4.8.1 (fedora f19) This warning is new in GCC 4.8, and I have been seeing a ton of them not just in boost,

RE: std::count leaked outside namespace std?

Here's a simple program: #include algorithm #include vector int main() { std::vectorint vec; count(vec.begin(), vec.end(), 0); // shouldn't this be std::count ? } The above compiles successfully, but I think it shouldn't. I expect a message like error: `count` not declared in scope

RE: Could we start accepting rich-text postings on the gcc lists?

Similarly for text-only vs. rich text. You may argue that there's no compatibility issue, but I disagree. As was pointed out upthread, when people use rich text, they often start to use colors or other mechanisms to express themselves, which can now be dependent on the rendering agent

C++11 no longer experimental

Hello, Now that the C++11 standard has been officially voted in, there is nothing  experimental about it any more. Would it be possible to remove the warning about GCC's C++11 support being experimental from http://gcc.gnu.org/projects/cxx0x.html, and to modify the __GXX_EXPERIMENTAL_CXX0X__

new C++11 features in GCC 4.7

Hi, I'm wondering, are there are other new C++11 features planned for GCC 4.7 besides Extended friend declarations and Explicit virtual overrides (which are marked as already implemented at http://gcc.gnu.org/projects/cxx0x.html)? Thanks, Nate

Re: Tracing C++ template instantiations‏

On 06/09/2011 03:48 PM, Jonathan Wakely wrote: When I'm working on complicated template code and debugging a mixture of bugs in my templates and ICEs in g++ caused by my buggy templates I sometimes wish I could see a dump of all the templates that the compiler is instantiating, so I can

gcc interprets C++0x initialization construct as function declaration

Hello, For the following code: struct S { int a; float b; }; struct T { T(S s) {} }; int main() { T t(S{1, 0.1}); // ERROR HERE } gcc 4.6 trunk gives the following errors (with the --std=c++0x option): decl.cpp: In function 'int main()': decl.cpp:14:10: error: expected ')'

internal compiler error in gcc trunk when using std::map

Hello, I've just build the gcc trunk and tried to compile some code that compiled fine with gcc 4.5. It gave an internal compiler error. I've reduced it to the following minimal test case: #include string #include map int main() { std::mapstd::string, int m; std::pairstd::string, int

g++ segfault when using C++0x feature‏

Hello, The attached minimal code (test.cpp) causes g++ to segfault. It uses the C++0x features variadic templates and initializer lists. The command used to compile it is: g++ -std=c++0x test.cpp The output is: test.cpp: In function ‘void f(const Args ...) [with Args = ]’: test.cpp:21:  

missing return statement

Hello, So many times I write code like this: SomeType function() { SomeType result; // do something with result return result; } except I often forget the return result statement. Why does gcc not give an error about this? If I compile with -Wall, it will give a WARNING saying

RE: missing return statement

On Thu, Mar 12, 2009 at 4:56 PM, Robert Dewar wrote: Nathan Ridge wrote: Why does gcc not give an error about this? If I compile with -Wall, it will give a WARNING saying control reaches end of non-void function. However, shouldn't it be an ERROR to return nothing from a function that's