Don't use "typedef struct" or "typedef union" about paho.mqtt.c HOT 4 CLOSED

I also read this:

http://stackoverflow.com/questions/10243149/why-is-typedef-struct-foo-foo-considered-harmful

where there are pros and cons described both ways.

from paho.mqtt.c.

I've done some reading around this as well and fwiw my view is that if it's a public struct then I would avoid using a typedef but for opaque structs it makes sense.

Having said that, I'm also a big fan of not breaking backwards compatibility unless really necessary.

from paho.mqtt.c.

If you use C++, you don't have to use the struct keyword. I know that this isn't C++, but I was trying to get to a similar position, which would still probably be my preference. I don't want to break backward compatibility - we'd have to go to a 2.0 release for that.

We could have a #define which omitted the typedefs, for those who really want to. The default would be to operate as we do today.

from paho.mqtt.c.

I'll consider this for future client implementations, or new versions, but not for now. Thanks.

from paho.mqtt.c.