Delivering safe C++ Bjarne Stroustrup Columbia University www.stroustrup.comOverview • The challenges of safety • What is “safety”? • C++ Evolution • with a focus on safety • C++ Core Guidelines of an unsigned integer loop variable or a narrowing conversion. • Timing errors: for example, delivering a result in 1.2ms to a device supposedly responding to an external event in 1ms. • Allocation of an unsigned integer loop variable or a narrowing conversion. • Timing errors: for example, delivering a result in 1.2ms to a device supposedly responding to an external event in 1ms. • Allocation

information assurance. Agile development practices can help the DoD to transform IT acquisition by delivering capabilities faster and responding more effectively to changes in operations, technology, and practices help to make progress and development more transparent, enabling improved decision making by delivering more timely and accurate information. However, Agile is not a panacea: it does not promise to produces a sprint backlog that defines the set of user stories each sprint team has committed to delivering. Development teams often have planning sessions periodically throughout the releases and sprints

relationship between uncertainty, risk, and change is far too complicated for such control when delivering IT systems, where complexity is overwhelming and the number of potential failure modes is high do people feel like there is risk in an Agile approach? They are worried about the schedule for delivering what they think of as FOC. The perceived risk is that the project will be “finished” late.  attached to the timing of FOC is just another example of the misconception that IT delivery is about delivering discrete, finished products. We want our FOC because we think that is the point at which we are

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by Apache ActiveMQ Artemis and will call it pre-acknowledge tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by Apache ActiveMQ Artemis and will call it pre-acknowledge tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by Apache ActiveMQ Artemis and will call it pre-acknowledge tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This example demonstrates how Apache ActiveMQ Artemis allows this with an extra the client consumes messages. For performance reasons clients normally buffer messages before delivering to the consumer via the receive() method or asynchronously via a message listener. If the consumer as soon as they are consumed. In these cases, updating the delivery count persistently before delivering the message would add an extra persistent step for each message delivered, implying a significant

and 2018, it lost a cumulative -$5.6B delivering ~540K vehicles. It went public in 2010 at a market cap of $1.6B. From 2019-2024, it then earned $40B delivering 6.7MM vehicles. Its market cap is now software to transform how users experience our products. Apple Intelligence also empowers users by delivering personal context that's relevant to them. And importantly, Apple Intelligence is a breakthrough will push breadth, stitching together knowledge across functions; specialists will push depth, delivering AI that speaks the language of compliance, contracts, and customer intent. The question isn’t

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by Apache ActiveMQ Artemis and will call it pre-acknowledge tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ

messages in event of failure, so it would make sense to acknowledge the message on the server before delivering it to the client. This extra mode is supported by Apache ActiveMQ Artemis and will call it pre-acknowledge tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ tcp://localhost:61616 |NAME |ADDRESS |CONSUMER_COUNT|MESSAGE_COUNT|MESSAGES_ADDED|DELIVERING_COUNT|MESSAGES_ACKED|SCHEDULED _COUNT|ROUTING_TYPE| |DLQ |DLQ