i really hate this idea that every non-trivial struct in c must be an opaque heap allocated pointer because people can't trust their users to read documentation, or what?
abi stability is another topic, and that one is more valid of a reason, but i'd still say it's not that hard, use sonames properly -- but if you *know* the struct definition will be changing a lot, then it's fair (but consider structuring your api differently, be modular and rely less on one single big struct type)
abi stability is another topic, and that one is more valid of a reason, but i'd still say it's not that hard, use sonames properly -- but if you *know* the struct definition will be changing a lot, then it's fair (but consider structuring your api differently, be modular and rely less on one single big struct type)
