Databases
StackOverflow2013
Postsdbo
POHowto handle typedefs without include headers in headers
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHowto handle typedefs without include headers in headers
    primarykey
    data
    text
    <p>As for working on a larger project, I want to throw in some own types (e.g. <code>myType</code>). The "rushing in"-approach would be, to put those typedefs into an header (lets say <code>myType.h</code>), together with a bunch of functions working on those types.</p> <p>If I use the new type somewhere, I include <code>myType.h</code> to my source-file. Fine.</p> <p>But if I want to use the new type somewhere as an argument in a function-signature, I need to include the <code>myType.h</code> to the header of the module containing the function. With one or another typedef, this seems to be okay for me, but the more types I have, the more includes in headers I need, possible including further header, while using type including other own types. This is resulting in what I call "<strong>dependency hell</strong>".</p> <p>Is there a clever, stylish, best practice, what-so-ever way to solve this dilemma? </p> <p>I'm aware of the possibility to pass those types as void-pointer, casting them back inside the function, but then I loose important type-checking from the compiler.</p> <p>Furher, <code>extern</code> is considered worst-practice around here.. </p> <p><strong>EDIT:</strong></p> <p>In detail:</p> <p><code>myType.h</code>:</p> <pre><code>#include "otherType.h" typedef struct { char Name[32]; int Size; otherType someType; } myType; processSomeHow(myType _myType, int NewSize); </code></pre> <p><code>otherType.h</code></p> <pre><code>#define SOME_CONST 32 typedef struct { [...] } otherType; </code></pre> <p><code>someModule.h</code>:</p> <pre><code>#include "myType.h" int specialProcessSomeHow(myType _myType); </code></pre> <p><code>someModule.c</code>:</p> <pre><code>int specialProcessSomeHow(myType _myType) { int Size = 64; return(processSomeHow(_myType, Size)); } </code></pre> <p>Now I include <code>otherType.h</code> indirectly to <code>someModule.h</code>, even worse, I include it to every module, that includes <code>someModule.h</code>. Now I have a <code>SOME_CONST</code> everywhere and it's hard to figure out, from where it comes. I have to maintain two include trees.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOliver
    1. USOliver
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHowto handle typedefs without include headers in headers
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHowto handle typedefs without include headers in headers
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO*`external` is considered worst-practice around here* Then maybe `extern` is fine ?
      singulars
      1. POHowto handle typedefs without include headers in headers
      1. UScnicutar
    2. COThe problem you are mentioning is a false dilemma. As long as you defensively name your typedefs and surround them with include guards there can never be a "dependency hell".
      singulars
      1. POHowto handle typedefs without include headers in headers
      1. UScnicutar
    3. COForward declarations + include guards will always help you deal with problems like these :)
      singulars
      1. POHowto handle typedefs without include headers in headers
      1. USLihO
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload