News for hackers. Stuff that matters.
Re:Why should I have written ZeroMQ in C, not C++ (part II) by rumcajz on Thursday August 30, 2012 @01:08PM (#4455614)
My point was that the trade-off is not something unavoidable. A better language could allow you to syntactically decouple the tightly coupled objects. See the example at the end of the article.
Re:Why should I have written ZeroMQ in C, not C++ (part II) by vampirechicken on Friday August 31, 2012 @10:11AM (#4459753)
I was actually agreeing with you, and elaborating on what you talked about.

I went back and read the bottom of the article. The Design Pattern people might call that a decorator. The ruby folks would use a mixin to monkey patch the person class. You're in good company.

The trade-offs are still code complexity + programmer time vs. memory use + run time. The more general you make something, the more overhead at run time.

Re:Why should I have written ZeroMQ in C, not C++ (part II) by dkersten on Thursday August 30, 2012 @02:41PM (#4456106)
A better language could allow you to...

And yet C is not this language.

Re:Why should I have written ZeroMQ in C, not C++ (part II) by mpyne on Thursday August 30, 2012 @03:31PM (#4456314)
And even if it was, C++ is nearly a superset of C. Write the part in C-style code which works best in C and then move on with your life...