I have hundreds (almost one thousand!) of \copydoc statements which are
producing the following warning message.
Warning: target testClassX::innerClassX::getYes() of \copydoc command not
found

Here is the situation.
There is a C++ class, called testClassX.cpp
Here are its contents:

// Start testClassX.cpp

namespace abc {

namespace def {
class testClassX::innerClassX {
  /*! \brief blah blah
   * \details prints stuff out
   */
  void printIt() {
        printStuff();
    }
  
  bool getYes() {
        return true;
   }
}

    testClassX::testClassX() {
        testClassX_ = new testClassX;
    }

    /*! \copydoc testClassX::InnerClassX::printIt() */
    void testClassX::printIt() {
        testClassX_->printIt();
    }

    /*! \copydoc Catalog::Impl::load() */
    bool testClassX::getYes() {
        return testClassX_->getYes();
    }

}
}

// End testClassX.cpp


The above example, when run through doxygen, yields:

Warning: target testClassX::innerClassX::getYes() of \copydoc command not
found
(However, there is no warning message for printIt(). Is this because it does
not return any parameters?)

Note that the class testClassX is declared in the .h file. 

What is wrong in the above example? How can I get rid of those \copydoc
related warnings?



--
View this message in context: 
http://doxygen.10944.n7.nabble.com/copydoc-warning-message-for-inner-class-target-of-copydoc-not-found-tp6344.html
Sent from the Doxygen - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to