Why should I have written ZeroMQ in C, not C++ (part I)

from 250bpm 250bpm

Just to be clear from the very beginning: This is not going to be a Torvalds-ish rant against C++ from the point of view of die-hard C programmer.I've been using C++ whole my professional career and it's still my language of choice when doing most projects.Now, almost 5 years later, I would like to publicly admit that using C++ was a poor choice and explain why I believe it is so.First, it's important to take into account that ZeroMQ was intended to be a piece of infrastructure with continuous uptime. It should never fail and never exhibit undefined behaviour. Thus, the error handling was of utmost importance. It had to be very explicit and unforgiving.

Who influenced this selection?What is this?

What the influencers are saying

  1. Debasish Ghosh

    149.0 days ago

    Why should I have written ZeroMQ in C, not C++ .. A useful rant http://t.co/AyCH7mlO via @prismatic

  2. Jonas Bonér

    149.0 days ago

    RT @debasishg: Why should I have written ZeroMQ in C, not C++ .. A useful rant http://t.co/AyCH7mlO via @prismatic

  3. Dion Almaer

    149.0 days ago

    "It seems that object-oriented languages are suited when rapid dev > the requirement for no undefined behaviour." http://t.co/icr4rvl1



Related Reading




InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.