Solution for C++ error c2039 is not a member of global namespace

Question

0.00/5 (No votes)

See more:

hi
Recently when I was writing c++ programs in VS 2010 I started getting the error
"

error c2039 is not a member of global namespace

" on separating the interface and implementation.

why would this happen?

What I have tried:

it was resolved as sooon as i changed the order of my # include directives. My header files went down and standard header files went up. the issue was resolved. I was lucky to have read this somewhere or may be, being meditative helped me.

Posted 22-Mar-17 1:22am

neelu7779

Updated 22-Mar-17 1:41am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

neelu7779 · Answer 1 · 2017-03-22T01:23:00

Solution 1

in the include section the standard header files should always precede the class files written by programmer.

Posted 22-Mar-17 1:23am

neelu7779

Jochen Arndt · Answer 2 · 2017-03-22T01:41:00

The common solution is to include those system and library header files on top of your header files that are required to compile the header file without errors.

That means that a source file containing only an include statement for your header file (probably after including stdafx.h; see below) should compile without errors.

Visual Studio is a little bit special here because many of the Windows system header files are usually included with stdafx.h when using pre-compiled headers. But including the same files again does not harm (they are skipped by guarding or using #pragma once).

Including all necessary header files in your header file ensures that it can be also used for other projects and when pre-compiled headers are disabled. While this might be not not necessary for a single project, it is good style and allows re-using for other projects.