4 ms·
Atomic Weapons: The C++ Memory Model and Modern Hardware
- Dewie 12y agoWildly off-topic, but I wonder if people like Sutter get tired of saying "c plus plus". It's a very wordy name, and words that start with "p" has got a certain punching quality that I don't know what is called. If I was a daily C++ programmer, I'd rather call it "c p p".
- santaclaus 12y agoMost of the C++ devs I interact with say "c p p", and our local C++ meetup is actually named CPP.
- MaulingMonkey 12y agoI believe I normally hear "c p p" when referencing C++ files (including in aggregate possibly referencing headers), but "c plus plus" when talking about the language proper, the standard, compilers, etc.
- jgh 12y agoi think if i worked with more C++ devs I'd call it "cpp" but since I don't "c plus plus" is better for clarity
- wffurr 12y agoIn phonetics, it's a "plosive".
- Retra 12y ago'CPP' makes me think 'C Preprocessor.'
- agumonkey 12y agoAs a dishonest Schemer, I call it (inc c), less wordy, far easier to say.
- 0xdeadbeefbabe 12y agoParen ink see paren?
- waterlesscloud 12y agoC++ was my goto daily language for about 10 years, though not as much any more. It all becomes one word, "seeplusplus" that you say pretty fast. It's only three syllables. And faster than "javascript". :-)
- cmollis 12y agoit's not as hard as saying 'objective C'.. although, oddly, not as painful as saying 'golang'.
- angersock 12y agoDaily reminder that anybody who, in C/C++ application code, doesn't hide their atomic ops, integer sizes, and simd directives behind compiler- and system-agnostic defines deserves to die in a motherfucking fire. EDIT: Downvote away...if you've ever had to migrate over a codebase that did this, you know exactly what I'm talking about.
- a_t48 12y agoBeing correct doesn't mean you get to be rude about it.
- angersock 12y agoSo, for certain categories of problems, I disagree. There's way too little acknowledgement in our industry of just how much suffering and anguish one or two chucklefucks on a codebase can inflict on their teammates. Using only the matter at hand as an example: "Rude" is waking somebody up to stand watch over a buggy system because it wasn't written properly and will seize up. "Rude" is wasting senior developer time on a refactor because the last person who touched the code used system calls and primitives only available on one specific compiler and one specific OS, and now the system has to change. "Rude" is injuring somebody because your embedded controller is using the wrong sized int for something, because it slipped through code review because somebody decided to use a #define that got changed between architecture upgrades and never fixed it. "Rude" is wasting a tester's day having them try to hop up and down over the same three feet of virtual space while trying to tap the attack key just right to repro a race-condition bug caused by some permutation of the above. 8. Hours. Of. Hopping. ~ When you write shitty software, you are hurting everyone else who might ever have to interact with it--so, uh, yeah, I get to be rude.
- stinos 12y agoso, uh, yeah, I get to be rude. No, you don't. Let me rephrase: I think it would be appreciated here, and for the sake of politeness and basic respect towards others, that you do not get rude. There are a thousands of other ways to write down how you feel about something without being rude, and people will still perfectly understand it. Moreover they are even more likely to pay proper attention to it if you are not rude.