This time I wrote up my retrospective plan. Read on to find out how it went. Continuing the theme of real retrospective examples, this post is another example of a real retrospective.

En blogg om bland annat segling och linux. Performance degradation after meltdown mitigation. I was worried about how slow my computer would be after applying the mitigations. So I measured the most important and common task for me - compiling c code. When I run it three times in a row I get.

And I plan to follow up on those in future posts, but I first wanted to make a comment of my own on the vulnerability note from cert. The scary thing is that if you are writing code that actually does encounter un.

You can still download the show. David Stone has spoken at C Now and Meeting C . What do you want to see in VS2015 Update 1. C Now 2014 - Removing Undefined behavior from integer operations. Meeting C 2014 - Writing robust code.

Guidelines and musings on C programming. Saturday, 15 November 2014. A function should have a single exit point at its end. Prefer a single exit point. In void functions, the single exit point should be the physical end of the function. In non-void functions, the single exit point should be a return statement at the last line of the function. The return statement should be simple and avoid implicit type conversions. In void function, a retu.