Gcc Error Extra
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring
Extra Qualification On Member -fpermissive C++
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask extra qualification in resume Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join extra qualification on member xcode them; it only takes a minute: Sign up extra qualification error in C++ up vote 54 down vote favorite 4 I have a member function that is defined as follows: Value JSONDeserializer::ParseValue(TDR type, const json_string& valueString); When I compile
C++ Cannot Be Overloaded
the source, I get: error: extra qualification 'JSONDeserializer::' on member 'ParseValue' What is this? How do I remove this error? c++ g++ compiler-errors share|improve this question edited Feb 27 '15 at 19:30 Ian R. O'Brien 3,10353058 asked Apr 12 '11 at 22:28 prosseek 42.4k105350627 add a comment| 4 Answers 4 active oldest votes up vote 97 down vote accepted This is because you have the following code: class JSONDeserializer { Value JSONDeserializer::ParseValue(TDR type, const json_string& valueString); }; This is
Gcc Options
not valid C++ but Visual Studio seems to accept it. You need to change it to the following code to be able to compile it with a standard compliant compiler (gcc is more compliant to the standard on this point). class JSONDeserializer { Value ParseValue(TDR type, const json_string& valueString); }; The error come from the fact that JSONDeserializer::ParseValue is a qualified name (a name with a namespace qualification), and such a name is forbidden as a method name in a class. share|improve this answer edited Dec 30 '13 at 13:11 answered Apr 12 '11 at 22:39 Sylvain Defresne 23.2k35574 Is there any way to make Visual Studio warn about this? –altumano Jan 23 '15 at 8:53 1 @altumano: No, but Cppcheck can do that and also detect non-ASCII characters in identifiers which helps maintain code more portable to gcc. –sharptooth Jan 26 '15 at 14:08 @sharptooth: thanks, Cppcheck can indeed detect those errors. There is even a Visual Studio plugin for Cppcheck (but it's buggy and do not detect in all files) –altumano Mar 6 '15 at 11:08 1 @altumano: Is it this thing github.com/VioletGiraffe/cppcheck-vs-addin ? If so could you please report the bug - that project is quite alive and there's good chance it will be fixed. –sharptooth Mar 6 '15 at 11:28 add a comment| up vote 11 down vote This means a class is redundantly me
risky or suggest there may have been an error. The following language-independent options do not enable specific warnings but control the kinds of diagnostics produced by GCC. -fsyntax-onlyCheck the code for syntax errors, fpermissive but don't do anything beyond that. -fmax-errors=nLimits the maximum number of error
G++ -g Flag
messages to n, at which point GCC bails out rather than attempting to continue processing the source code. If extra qualification in cv n is 0 (the default), there is no limit on the number of error messages produced. If -Wfatal-errors is also specified, then -Wfatal-errors takes precedence over this option. -wInhibit all warning http://stackoverflow.com/questions/5642367/extra-qualification-error-in-c messages. -WerrorMake all warnings into errors. -Werror=Make the specified warning into an error. The specifier for a warning is appended; for example -Werror=switch turns the warnings controlled by -Wswitch into errors. This switch takes a negative form, to be used to negate -Werror for specific warnings; for example -Wno-error=switch makes -Wswitch warnings not be errors, even when -Werror is in effect. The https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html warning message for each controllable warning includes the option that controls the warning. That option can then be used with -Werror= and -Wno-error= as described above. (Printing of the option in the warning message can be disabled using the -fno-diagnostics-show-option flag.) Note that specifying -Werror=foo automatically implies -Wfoo. However, -Wno-error=foo does not imply anything. -Wfatal-errorsThis option causes the compiler to abort compilation on the first error occurred rather than trying to keep going and printing further error messages. You can request many specific warnings with options beginning with ‘-W’, for example -Wimplicit to request warnings on implicit declarations. Each of these specific warning options also has a negative form beginning ‘-Wno-’ to turn off warnings; for example, -Wno-implicit. This manual lists only one of the two forms, whichever is not the default. For further language-specific options also refer to C++ Dialect Options and Objective-C and Objective-C++ Dialect Options. Some options, such as -Wall and -Wextra, turn on other options, such as -Wunused, which may turn on further options, such as -Wunused-value. The combined effect of positive and negative forms is that more specific options
or suggest there may have been an error. You can request many specific warnings with options beginning -W, for example -Wimplicit to request warnings on implicit declarations. Each of these specific warning options also has a negative form beginning -Wno- to http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Warning-Options.html turn off warnings; for example, -Wno-implicit. This manual lists only one of the two forms, whichever is not the default. The following options control the amount and kinds of warnings produced by GCC; for http://alt.comp.lang.learn.c-cpp.narkive.com/MSBDh7Wu/gcc-error-extra-qualification-x-on-member further, language-specific options also refer to C++ Dialect Options and Objective-C Dialect Options. -fsyntax-onlyCheck the code for syntax errors, but don't do anything beyond that. -pedanticIssue all the warnings demanded by strict ISO C and extra qualification ISO C++; reject all programs that use forbidden extensions, and some other programs that do not follow ISO C and ISO C++. For ISO C, follows the version of the ISO C standard specified by any -std option used. Valid ISO C and ISO C++ programs should compile properly with or without this option (though a rare few will require -ansi or a -std option specifying the required version of extra qualification on ISO C). However, without this option, certain GNU extensions and traditional C and C++ features are supported as well. With this option, they are rejected. -pedantic does not cause warning messages for use of the alternate keywords whose names begin and end with __. Pedantic warnings are also disabled in the expression that follows __extension__. However, only system header files should use these escape routes; application programs should avoid them. See Alternate Keywords. Some users try to use -pedantic to check programs for strict ISO C conformance. They soon find that it does not do quite what they want: it finds some non-ISO practices, but not all—only those for which ISO C requires a diagnostic, and some others for which diagnostics have been added. A feature to report any failure to conform to ISO C might be useful in some instances, but would require considerable additional work and would be quite different from -pedantic. We don't have plans to support such a feature in the near future. Where the standard specified with -std represents a GNU extended dialect of C, such as gnu89 or gnu99, there is a corresponding base standard, the version of ISO C on which the GNU extended dialect is based. Warnings from -pedantic
was compiling astyle http://astyle.sourceforge.net/and boehm gc http://www.hpl.hp.com/personal/Hans_Boehm/gc/from sourcesand both make breaked with errorerror: extra qualification 'X::' on member 'bar'(X and bar my names)after I edited both files make could end successfullythis example is a simple reproduction of this behaviourcat broken.cpp#include