Hi Leo,

Please mention the version of doxygen you are using and attach
a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem.

Note that I tried a simple example:

---------------------------------------------------

namespace lfc1 
{ 
  namespace datetime
  {
    class CDateGet
    {
      public:
        CDateGet(size_t avRelease=0);
        CDateGet(const CDateGet &);
    };
  }
}

//-------------------------------------

using namespace lfc1::datetime;

CDateGet::CDateGet(size_t avRelease)
{
}

CDateGet::CDateGet(const CDateGet &)
{
}

---------------------------------------------------
But that worked fine.

I'm using #define's for the namespace names which are defined in include files used by my source code.  Is doxygen able to resolve namespace names that use #define's?

Just wondering if this is what is causing the problem.

The Doxygen version is 1.7.3.

I will need to try and generate a cut down version of my project which exhibits the problem.  This may take some time because my project is currently already large.

All of the classes in my project are coded in the following manner:

  datetime.hpp:
  -------------

    #define LFC1_DATETIME_NS_BEGIN namespace lfc1 { namespace datetime
    #define LFC1_DATETIME_NS_END }}

  cdate.hpp:
  ----------

    LFC1_DATETIME_NS_BEGIN

    class CDateGet
    {
      public:
        CDateGet(size_t avRelease=0);
        ~CDate();
    };

    LFC1_DATETIME_NS_END

  cdateget.cpp:
  -------------

    LFC1_DATETIME_NS_BEGIN

    CDateGet(size_t avRelease)
    {
    }

    ~CDateGet()
    {
    }

    LFC1_DATETIME_NS_END

My project already contains 6 libraries which follow the coding style above.  There are no issues with the first 5 libraries.  I have only encountered the problem I described on the last library.  I tried replacing the uses of the #define's with their actual values in the first file which contained the issue and the problem went away.  Unfortunately, this is not my desired solution because there is a good reason for using the #define's.

FYI: you can let doxygen ignore the macros by using its preprocessor, see
http://www.doxygen.org/preprocessing.html
But I don't think this is the real problem.

FYI, I removed the #define's for the namespaces and all the problems that I was encountering went away.

Shall we close the bug ?

OK, you may close the bug.

Closing on request.