Re: [Doxygen-users] Problems with javadoc-style links

[Bogdan I. <bo...@ne...>]

Hello again,

A similar problem: a link of the form

{@link #mf(std::string)}

generates the same kind of warning:

D:/bog/work/tmp2/Test.h:10: Warning: link to unknown entity `string' in the
documentation of this entity!

In this case however, the resulting HTML will contain only 'string'
instead of 'mf(std::string)', which can get quite confusing.

{@link #mf(string)} works fine.

Cheers,
Bogdan



----- Original Message -----
From: "Bogdan Iordanescu" <bo...@ne...>
To: <dox...@li...>
Sent: Thursday, June 14, 2001 5:14 PM
Subject: [Doxygen-users] Problems with javadoc-style links


> Hi,
>
> I encountered a couple of problems trying to use the javadoc-style {@link
> ...} construct.
>
> An example for one of the problems:
>
> /**
>  * This is a test class. Details.
>  */
> class Test
>    {
> public:
>    /**
>     * A member function. This function uses {@link #m}.
>     */
>    void mf();
>
> private:
>    /**
>     * A data member. Details.
>     *
>     * @see #mf()
>     */
>    int m;
>    };
>
> The link to 'm' generates the following error message from Doxygen:
>
> D:/bog/work/tmp2/Test.h:10: Warning: link to unknown entity `m' in the
> documentation of this entity!
>
> A link to a target that contains parentheses, like {@link #mf()}, works
> fine. Also, just inserting #m in the documentation works fine, but I need
> to use the @link tag for various compatibility reasons.
>
> The other problem is that Doxygen doesn't seem to support the construct
> {@link target label}
> This generates the above error message, pointing to 'label'.
>
> Am I doing something wrong? Are these known problems?
>
> I'm using Doxygen 1.2.8.1 on NT4.
>
> Thanks,
> Bogdan
>
>
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> http://lists.sourceforge.net/lists/listinfo/doxygen-users