Théophile Helleboid | 3 Dec 21:09 2007
Picon

Fwd: Segfault with doxygen with last libcaca doc

Hello,
I have a bug with the libcaca software, using doxygen.
What I've done :

cd libcaca-svn
svn up
(svn rev 1418)
make
[...]
make[2]: entrant dans le répertoire « /home/chtitux/src/libcaca-svn/doc »
doxygen doxygen.cfg
make[2]: *** [stamp-doxygen] Erreur de segmentation

I'm on Gentoo, gcc 4.1.2.
Due to Gentoo, libraries may be broken (I don't know)
so, ldd `which doxygen`
chtitux <at> localhost ~/src/libcaca-svn $ ldd `which doxygen`
       linux-gate.so.1 =>  (0xb7f63000)
       libstdc++.so.6 =>
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6 (0xb7e58000)
       libm.so.6 => /lib/libm.so.6 (0xb7e32000)
       libgcc_s.so.1 =>
/usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1 (0xb7e27000)
       libc.so.6 => /lib/libc.so.6 (0xb7cf7000)
       /lib/ld-linux.so.2 (0xb7f64000)

and
chtitux <at> localhost ~/src/libcaca-svn $ doxygen --version
1.5.2

(Continue reading)

Robert Dailey | 3 Dec 21:45 2007
Picon

HOW TO: JAVADOC_AUTOBRIEF with no brief?

I have the following code:

class directx_exception : public std::exception
{
public:
        /// <at> param errorCode HRESULT returned by the directx function that is the source of the exception.
        /// <at> param message A custom user message.
        /// <at> param line The line number representing the location of the exception.
        /// <at> param file A file name representing the location of the exception.
        directx_exception( HRESULT errorCode, const char* message, unsigned int line, const char* file );
};

However, doxygen treats the first <at> param as the brief description since I have JAVADOC_AUTOBRIEF set to YES. This is the correct behavior given the functionality description of AUTOBRIEF, however I'm wondering how I can modify the settings file or the code documentation to not treat the first <at> param as a brief? Basically, I want the code above to have *no* brief description while still keeping AUTOBRIEF set to YES. I would really hate to have to do something cheesy like "///." to make it skip the brief.

Thanks.

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Doxygen-users mailing list
Doxygen-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Paul Joireman | 3 Dec 22:03 2007

Re: HOW TO: JAVADOC_AUTOBRIEF with no brief?

If you set JAVADOC_AUTOBRIEF to NO, the first line will not be considered as the brief description.   When you want a brief use the

\brief tag, when you don’t want a brief description leave this out and no brief will be generated.   However, this does require you to change other functions that have the first line as a brief description.

 

--Paul

 

From: doxygen-users-bounces <at> lists.sourceforge.net [mailto:doxygen-users-bounces <at> lists.sourceforge.net] On Behalf Of Robert Dailey
Sent: Monday, December 03, 2007 2:46 PM
To: doxygen
Subject: [Doxygen-users] HOW TO: JAVADOC_AUTOBRIEF with no brief?

 

I have the following code:

class directx_exception : public std::exception
{
public:
        /// <at> param errorCode HRESULT returned by the directx function that is the source of the exception.
        /// <at> param message A custom user message.
        /// <at> param line The line number representing the location of the exception.
        /// <at> param file A file name representing the location of the exception.
        directx_exception( HRESULT errorCode, const char* message, unsigned int line, const char* file );
};

However, doxygen treats the first <at> param as the brief description since I have JAVADOC_AUTOBRIEF set to YES. This is the correct behavior given the functionality description of AUTOBRIEF, however I'm wondering how I can modify the settings file or the code documentation to not treat the first <at> param as a brief? Basically, I want the code above to have *no* brief description while still keeping AUTOBRIEF set to YES. I would really hate to have to do something cheesy like "///." to make it skip the brief.

Thanks.

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Doxygen-users mailing list
Doxygen-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Robert Dailey | 3 Dec 22:21 2007
Picon

Re: HOW TO: JAVADOC_AUTOBRIEF with no brief?

In my original inquiry I had mentioned that I would like to work around this without setting JAVADOC_AUTOBRIEF to NO. So far, I find that this works:



class directx_exception : public std::exception
{
public:
        ///.
        /// <at> param errorCode HRESULT returned by the directx function that is the source of the exception.
        /// <at> param message A custom user message.
        /// <at> param line The line number representing the location of the exception.
        /// <at> param file A file name representing the location of the exception.
        directx_exception( HRESULT errorCode, const char* message, unsigned int line, const char* file );
};

However, doing it this way has 2 issues:

1) It leaves an arbitrary carriage return under each member of the class (additional wasted space in the HTML output).
2) It causes the following unnecessary warning in the doxygen output: "Warning: End of list marker found without any preceding list items"

Any ideas?

On Dec 3, 2007 3:03 PM, Paul Joireman <joireman <at> fnal.gov> wrote:

If you set JAVADOC_AUTOBRIEF to NO, the first line will not be considered as the brief description.   When you want a brief use the

\brief tag, when you don't want a brief description leave this out and no brief will be generated.   However, this does require you to change other functions that have the first line as a brief description.

 

--Paul

 

From: doxygen-users-bounces <at> lists.sourceforge.net [mailto:doxygen-users-bounces <at> lists.sourceforge.net ] On Behalf Of Robert Dailey
Sent: Monday, December 03, 2007 2:46 PM
To: doxygen
Subject: [Doxygen-users] HOW TO: JAVADOC_AUTOBRIEF with no brief?

 

I have the following code:

class directx_exception : public std::exception
{
public:
        /// <at> param errorCode HRESULT returned by the directx function that is the source of the exception.
        /// <at> param message A custom user message.
        /// <at> param line The line number representing the location of the exception.
        /// <at> param file A file name representing the location of the exception.
        directx_exception( HRESULT errorCode, const char* message, unsigned int line, const char* file );
};

However, doxygen treats the first <at> param as the brief description since I have JAVADOC_AUTOBRIEF set to YES. This is the correct behavior given the functionality description of AUTOBRIEF, however I'm wondering how I can modify the settings file or the code documentation to not treat the first <at> param as a brief? Basically, I want the code above to have *no* brief description while still keeping AUTOBRIEF set to YES. I would really hate to have to do something cheesy like "///." to make it skip the brief.

Thanks.


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Doxygen-users mailing list
Doxygen-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Dimitri van Heesch | 3 Dec 22:22 2007
Picon

Doxygen-1.5.4-20071203 in SVN

Hi,

In this update the following has changed:
------------------------------------------------------------------------------
+ ADD: Added compilation support for MacOSX 10.5 (Leopard) in combination with
       Xcode 3.
+ ADD: Added support for docsets, which allow integration of doxygen generated
       API documentation in Xcode 3. new options:
       - GENERATE_DOCSET: enables/disables the feature
       - DOCSET_FEEDNAME: sets the provider/suite name under which the set is
                          listed.
       - DOCSET_BUNDLE_ID: A unique name for the docset.
       See the configuration file or manual for more details.
+ ADD: id 493467: Added compilation support 64bit Solaris machines in 
       combination with Sun's own compiler (thanks to Heiko Jansen).
+ BUG: id 490766: Fixed compile error in fortranscanner.l which occurred for
       some compilers.
+ BUG: id 493249: using a namespace (or fortran module) caused the namespace
       to appear in the documentation as if it was defined.
+ BUG: id 494187: Doxygen could crash due to an infinite recursion when
       using tag files. 
+ BUG: id 494599: When updating a config file an extra space was added just
       before the end of a quoted string.
+ BUG: id 500227: Wrong output generated for Objective-C methods with
       multiple arguments for LaTeX or RTF output.
+ BUG: id 500635: Project name is no longer placed before each top level
       item in the treeview and other indices.
+ BUG: Fixed a preprocessor bug where the line numbers of a definition could
       get out of sync with the source code.
+ BUG: Fixed potential crash bug due to wrong pointer check.
------------------------------------------------------------------------------
Enjoy,
  Dimitri

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
Petr Prikryl | 4 Dec 10:07 2007
Picon

Windows binaries available for Doxygen-1.5.4-20071203 in CVS

Hi,

If interested, you can download the doxygen binaries
compiled for MS Windows from

  http://doxygen.sourceforge.net/dl/doxygen-1.5-cvs/

This is the place where you should find also the next
releases.  Name of the archive file is 

    doxygenw20071203_1_5_4.zip.

The related translator report can be found inside
the archive tr20071203_1_5_4.zip.

The binaries are NOT created automatically, so it may
happen that some newer CVS sources were not compiled
because I am not present to do that or I forgot... ;)

Regards,
    Petr

--

-- 
Petr Prikryl (prikrylp at skil dot cz)

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
Clemens Feige | 4 Dec 13:00 2007

Re: Doxygen-1.5.4-20071203 in SVN

On 3 Dec 2007 at 22:22, Dimitri van Heesch wrote:

> + BUG: Fixed a preprocessor bug where the line numbers of a definition could
>        get out of sync with the source code.

Does this have a Bug-ID? I could not find it with a text search in 
Bugzilla.

I am asking because on Tue, 10 Oct 2006 I send a issue to the list 
titled: "Wrong line number references with #include directive". 

I got no reply and was not sure whether this could be a bug, so I 
didn't open a bug issue. 

> Enjoy,
Sure.

Best greetings
Clemens 

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
Kevin McBride | 4 Dec 12:39 2007
Picon

RPMs for 1.5.4-3 Officially Released

doxygen RPMs 1.5.4-3, reflecting doxygen version 1.5.4-20071203, has
been released.

You can download the RPMs from the following URL:

http://www.planetsaphire.com/rpms/doxygen

Or via anonymous FTP:

ftp://ftp.planetsaphire.com/doxygen

- KJM

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
Robert Dailey | 6 Dec 22:19 2007
Picon

Question about detailed descriptions for template classes.

Hi,

I noticed in a few tests of mine that for non-template classes, the class header does not show up under the detailed description section. However, if you turn the class into a template, it redundantly has the header of the class right under the detailed description. For example:

/// <at> detail Some details....
class foo
{
};

Output shows up as follows in HTML:

Detailed Description

Some details....

Now if I change the code snippet above to this:

/// <at> detail Some details....
template< typename T >
class foo
{
};

The output in HTML will now look like this:

Detailed Description

template< typename T >
class foo< T >

Some details....

Why does this happen? Is there a way I can disable the class header from showing up under the detailed description for template classes?

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Doxygen-users mailing list
Doxygen-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
Darren Debono | 7 Dec 17:50 2007

Re: Doxygen-1.5.4-20071203 in SVN

On 3 Dec 2007, at 21:22, Dimitri van Heesch wrote:

> + BUG: id 500635: Project name is no longer placed before each top  
> level
>        item in the treeview and other indices.

Using the Windows binary released a few days ago, I find that the  
project name is still placed before each item in the bookmark bar of  
a PDF document. Was this bug fix supposed to address this too?

Thanks,

Darren

-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

Gmane