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 8971867
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 15, 20262026-06-15T18:04:18+00:00 2026-06-15T18:04:18+00:00

I have this PACKED macro , that receives a struct definition and returns it

  • 0

I have this PACKED macro, that receives a struct definition and returns it with a compiler annotation to make it packed.

For example:

/**
 * ...
 */
PACKED(struct A {
    /**
     * ...
     */
    int x;
});

I have tried several Doxygen options to include that documentation, but I’ve had no success so far. Closest I’ve come up with is this:

ENABLE_PREPROCESSING = YES
PREDEFINED = PACKED(type)=type
MACRO_EXPANSION = YES

But that messes up the struct and members’ documentation (confirmed via doxygen -d Preprocessor).

Ideas?

  • 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-06-15T18:04:19+00:00Added an answer on June 15, 2026 at 6:04 pm

    Turns out it’s a bug in Doxygen.

    One possible workaround is to use @class, and so on.

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

Sidebar

Related Questions

In our code, we have a 16-byte packed struct that we call ISOTIME: typedef
In Delphi I have a structure like this: TCustomerInfo = Packed Record CustomerNo: Integer;
I have this Tags table CREATE TABLE IF NOT EXISTS `Tags` ( `id_tag` int(10)
Say that I have a long, expensive query, packed with conditions, searching a large
Lets say I have some domain objects that will need to be serialized/packed using
I have a minified/packed javascript file which is causing problems. The issue is that
I have the following struct: struct foo { int a; char b; }; It
I have a macro in my excel workbook that updates a specific record in
Is this even possible? basically I have a c++ application which sends packed 32
So I have this problem when I run a script with PHP PDO that

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.