3 ms·
I don't think the author is pushing for a standard. But depending on the desired intent one would be preferable to the other. for example a typedef would be u
by dvhh 7y ago
I don't think the author is pushing for a standard.
But depending on the desired intent one would be preferable to the other.
for example a typedef would be used to hide the complexity for an opaque pointer.
- deaddodo 7y agoI parsed that as two instructions: Do not use a typedef to hide a pointer Do not use a typedef to avoid writing “struct” Nothing to do with opaque pointers directly. And considering it's titled "Principles for C programming", it would seem intended as some sort of ruleset.