In C, is it good form to use typedef for a pointer?

by

If the pointer is never meant to be dereferenced or otherwise manipulated directly — IOW, you only pass it as an argument to an API — then it’s okay to hide the pointer behind a typedef.

Otherwise, it’s better to make the “pointerness” of the type explicit.

More Related Contents:

  1. C typedef of pointer to structure
  2. Is typedef’ing a pointer type considered bad practice? [duplicate]
  3. Unit testing for a function (tolower) using pointers
  4. Why this program is crashing?
  5. C pointer to another struct
  6. Segmentation fault using scanf() [closed]
  7. Returning an array using C
  8. Arrow operator (->) usage in C
  9. Why use double indirection? or Why use pointers to pointers?
  10. Using the equality operator == to compare two strings for equality in C [duplicate]
  11. printf(“%p”) and casting to (void *)
  12. Are typedef and #define the same in c?
  13. Exceptions to array decaying into a pointer?
  14. Pointer address in a C multidimensional array
  15. C: pointer to struct in the struct definition
  16. What is ‘forward declaration’ and the difference between ‘typedef struct X’ and ‘struct X’?
  17. Pointer/Address difference [duplicate]
  18. Enforce strong type checking in C (type strictness for typedefs)
  19. Array increment operator in C
  20. const usage with pointers in C
  21. C++ typedef interpretation of const pointers
  22. how to get hexdump of a structure data
  23. Using Double Pointers after memory allocated within function
  24. Returning this pointer from a function
  25. Do these statements about pointers have the same effect?
  26. How to initialize a pointer to a struct in C?
  27. Reliably determine the number of elements in an array
  28. Lvalue required error
  29. Directly assigning values to C Pointers
  30. Cast T[][] to T*

Leave a Comment