Re:First chapter of Kernighan and Donovan's new Go book [pdf]
by TillE on Monday October 19, 2015 @04:47PM
(#10415616)
I'm guilty of this when writing C. I really have no desire to learn the language properly (it's hard enough to fit C++ in my brain), so I'll just follow the patterns others have set.
Microsoft does stuff like:
typedef struct _FOO {
...
} FOO, *PFOO;
Yeah ok fine, I'll do that.
Re:First chapter of Kernighan and Donovan's new Go book [pdf]
by to3m on Monday October 19, 2015 @04:53PM
(#10415659)
When doing this in your own libraries, be sure to document how to generate the struct tag name from the typedef name. (MS don't do this - but they're not consistent about it anyway.) Then when people see a typedef'd struct used somewhere in a header, they'll know how to forward declare it in their own headers.
Re:First chapter of Kernighan and Donovan's new Go book [pdf]
by voltagex_ on Monday October 19, 2015 @11:07PM
(#10417182)
What's forward declaring mean?
Or cargo-culting.
edit: wow somebody felt threatened. I have no shame stating that I cargo-culted exactly that for a while before I actually wondered what I was doing.