Jason Mills | 8 Mar 2005 20:17
Picon
Picon

Doxygen and C++/.NET

Two few related questions:

- Have anyone used doxygen with Managed C++ (.NET)? If so, are there any 
filters available to handle managed C++ keywords, such as __interface?

- Will there ever be support for the soon to be available C++/CLI?

Thanks,
Jason

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Jason Mills | 9 Mar 2005 13:14
Picon
Picon

Re: Doxygen and C++/.NET

My apologies. I meant to post the following to the user group!

Jason

 > Two few related questions:
 >
 > - Have anyone used doxygen with Managed C++ (.NET)? If so, are there
 >   any filters available to handle managed C++ keywords, such as
 >   __interface?
 >
 > - Will there ever be support for the soon to be available C++/CLI?

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Xavier Outhier | 11 Mar 2005 09:21
Picon

Problem French accent under linux

Hi,

I got a user feedback about a problem for vizualising
the HTML doc in French under Linux (but it's correct
under Windows).

She made the following settings:
  USE_WINDOWS_ENCODING set to NO
  OUTPUT_LANGUAGE set to French

I feel the problem arise because I'm under Windows, using
French ASCII in the translator_fr.h.

I have two questions:
  -1 Will it solve the problem if I use the HTML entity
     in the header file?

  -2 Will it not disturb the other output: Latex, RTF or
     whatever.
     If yes how to solve the problem.

Xavier  - the French "localisator"

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
Petr Prikryl | 11 Mar 2005 12:33
Picon

RE: Problem French accent under linux

Hi Xavier,

Xavier Outhier wrote...
> [...]
> I got a user feedback about a problem for vizualising
> the HTML doc in French under Linux (but it's correct
> under Windows).
> 
> She made the following settings:
>   USE_WINDOWS_ENCODING set to NO
>   OUTPUT_LANGUAGE set to French
> 
> I feel the problem arise because I'm under Windows, using
> French ASCII in the translator_fr.h.

My guess is that French encoding for Unix is different
than French encoding for Windows. This means that
your translator should return the strings differently.
based on the USE_WINDOWS_ENCODING. It is 
only a configuration parameter that _can_ be tested
in your translator_fr.h.

If the encodings for Windows/Unix are not identical, 
the idLanguageCharset() should test the 
USE_WINDOWS_ENCODING and return the
appropriate string. In such case, you should
also define something like decode() that
also tests the USE_WINDOWS_ENCODING 
and converts encoding of strings returned 
by the translator methods. Have a look 
(Continue reading)

Picon
Favicon

Russian translation update

	Hi!
	translator_ru attached.
Attachment (rus.tgz): application/x-compressed, 10 KiB
Picon
Favicon

RE: Doxygen: Translator cz, kr, ru

	Hi!
	Petr, you russian is good! But when I check this, I do not find decode in last function, so new russian update attached.

-----Original Message-----
From: Petr Prikryl [mailto:Prikryl <at> skil.cz] 
Sent: Tuesday, March 15, 2005 11:25 AM
To: Dimitri van Heesch
Cc: Челпанов Александр Витальевич; jung5000 <at> gmail.com
Subject: Doxygen: Translator cz, kr, ru

Hi Dimitri,
... and copied "Hi" to Alexandr and SooYoung (is this the first name?)

I am sending the updated translator_cz.h (again -- forgot to change the base class).

I did a minor correction of comment in
the Russian translator. It is the one that was posted recenly in doxydev mailing list. 
(I did it when looking inside; the Decode() changed to decode() -- for Alexandr.
I was just curious whether jEdit will display the azbuka characters and whether I am still able to read and
understand the Russian language ;).

I have slightly corrected the Korean
translator to use newer translator adapter, as reported by translator.py. (No, I cannot read the Korean
texts. And it is not the jEdit fault  ;)

I have changed the line endings of all
mentioned translators to unix ones.

Regards,
  Petr
(Continue reading)

Picon
Favicon

Problems at last release?...

	Hi!
Is there a bug or new funtionality?

1. The doxygen comments on code
-----------------------------------
/*!
 * \brief aaaa
 * \note qqq
 */
class A{}
-----------------------------------
didn't look same as code 
-----------------------------------
/*!
 * \brief aaaa
 *
 * \note qqq
 */
class A{}
-----------------------------------
I think, that new tag end previous tag.

2. The doxygen comments on code
-----------------------------------
/*! 
 *\brief 1111
 *
 * text
 */
class A{};
(Continue reading)

Dimitri van Heesch | 15 Mar 2005 19:58
Picon
Gravatar

Re: Problems at last release?...

On Tue, 15 Mar 2005 14:10:20 +0300, Челпанов Александр Витальевич
<cav <at> cryptopro.ru> wrote:
>         Hi!
> Is there a bug or new funtionality?

Bugs, the first pass comment scanner was completely rewritten
(separated from the language parser), so still expect some problems in
corner cases. But please report them in the way you did and I'll fix
them ASAP.

Regards,
  Dimitri

> 
> 1. The doxygen comments on code
> -----------------------------------
> /*!
>  * \brief aaaa
>  * \note qqq
>  */
> class A{}
> -----------------------------------
> didn't look same as code
> -----------------------------------
> /*!
>  * \brief aaaa
>  *
>  * \note qqq
>  */
> class A{}
(Continue reading)

Picon
Favicon

RE: Problems at last release?...

	Hi!
	Thank's. Work fine. 

-----Original Message-----
From: Dimitri van Heesch [mailto:doxygen <at> gmail.com] 
Sent: Tuesday, March 15, 2005 9:59 PM
To: Челпанов Александр Витальевич
Cc: doxydev
Subject: Re: [Doxygen-develop] Problems at last release?...

On Tue, 15 Mar 2005 14:10:20 +0300, Челпанов Александр Витальевич
<cav <at> cryptopro.ru> wrote:
>         Hi!
> Is there a bug or new funtionality?

Bugs, the first pass comment scanner was completely rewritten (separated from the language parser), so
still expect some problems in corner cases. But please report them in the way you did and I'll fix them ASAP.

Regards,
  Dimitri

> 
> 1. The doxygen comments on code
> -----------------------------------
> /*!
>  * \brief aaaa
>  * \note qqq
>  */
> class A{}
> -----------------------------------
(Continue reading)

Rob Holland | 21 Mar 2005 18:43
Picon
Favicon

doxygen patch for always anchoring lines in HTML output

Hi,

As part of my work in adding features to doxygen to make it useful for
spotting common coding mistakes I'd like to ask that the attached patch
be applied. It makes sure that all lines have anchors in the HTML so
that I can refer to any source line from a source scanner report, such
as the output of rats/flawfinder and so on.

An example doxygen output with this patch and its use can be seen at:

http://dev.gentoo.org/~tigger/audit/sendmail_8_13_1_tar_gz/

I apologise for the uglyness of that page, but I'm far from the point in
my project where I start worrying about visual appeal ;)

You will see that clicking on any source code line will take you to the
relevant line in the doxygen-marked-up source code.

I have to say doxygen is an excellent utility. Kudos :)

Thanks,

Rob

--

-- 
rob holland - [ tigger <at> gentoo.org ] - Gentoo Audit Team
[ 5251 4FAC D684 8845 5604  E44F D65C 392F D91B 4729 ]

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
(Continue reading)


Gmane