Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3600756
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T20:32:08+00:00 2026-05-18T20:32:08+00:00

We have a function header format that we have to follow. It basically looks

  • 0

We have a function header format that we have to follow. It basically looks like this

/**
* Name: blah
*
* Parameters:
*       int foo
*       bool bar
*
* .....

We are attempting to generate some documents with doxygen, but one issue is that when we change he code to:

/**
* Name: blah
*
* Parameters:
*  \param  int foo
*  \param  bool bar
*
* .....

When Doxygen generates the html comments, it adds the Parameters title. We are required to have line 4, so this creates documents with 2 lines that say Parameters, the first is from line 4 and the second Doxygen auto inserts.

What I’m hoping I can do is either have Doxygen ignore line 4 or add have it not insert it’s own “Parameters:” title. Anyone know if this is possible?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T20:32:09+00:00Added an answer on May 18, 2026 at 8:32 pm

    The simple solution is to remove the “Parameters:” text altogether; it is entirely redundant since the Doxygen mark-up makes it perfectly clear that they are parameters!

    For that matter the “Name:” label is entirely redundant too, and forces you to place the name in both the comment and the code. Why would you need that? It’s name is right there in the code. It is an unnecessary comment maintenance headache, and Doxygen will use teh name in the code not the name in the comment in the generated documentation.

    If you must attempt to mix your existing format with a Doxygen compatible format it would be easier to use C++/C99 line comments rather than block comments; most C compilers support them:

    // Name: blah
    //
    // Parameters:
    /// \param  foo Description of foo
    /// \param  bar Description of bar
    

    Note \param <type> <name> is not correct Doxygen syntax; it is \param <name> <description>. Doxygen gets the type from the code; again specifying the type in the comment is entirely redundant, and another maintenance headache.

    I would strongly suggest that you employ a more Doxygen and maintenance friendly function boiler-plate altogether. I use the following basic form (for what its worth):

    //! @brief  Brief description
    //!
    //! Full description if necessary.
    //! @param p1    p1 description
    //! @param p2    p2 description
    //! @return Return value description
    int foobar( int p1, int p2 ) ;
    

    Obviously whether you use /// or //! and \ or @ is a matter of preference.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a function that looks like this class NSNode { function insertAfter(NSNode $node)
I have function like this in my header function bingframe() { var iframe =
I have a function that takes, amongst others, a parameter declared as int privateCount
Okay so i have a packed a proprietary binary format. That is basically a
I have a stored procedure with the following header: FUNCTION SaveShipment (p_user_id IN INTEGER,
I have a function that gives me the following warning: [DCC Warning] filename.pas(6939): W1035
I have a function that gets x(a value) and xs(a list) and removes all
I have a function, parseQuery, that parses a SQL query into an abstract representation
I have a function pointer defined by: typedef void (*EventFunction)(int nEvent); Is there a
I have a function that I use called sqlf(), it emulates prepared statements. For

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.