Popular Myths about C++, Part 1

Post by throwawayaway » Tue, Dec 09, 2014, 11:55 PM UTC

pjmlp wrote: post #118

throwawayaway wrote: post #58

Earlier quoted context omitted.

would it be fair to say you have just described references, or do I have to go and lookup this algol/mesa stuff?

Some examples using Modula-2, a Mesa's successor. How it allows for all the C pointer features, while adding a little bit more safety. MODULE examples; IMPORT Terminal, SYSTEM; (* procedure with reference parameter, no need for pointers *) PROCEDURE ChangeParam (VAR changeMe: CARDINAL); BEGIN changeMe := 25; END ChangeParam; (* procedure with a slice, bounds given by HIGH(changeMe) and LOW(changeMe). also a string in…

Post by throwawayaway » Wed, Dec 10, 2014, 12:09 AM UTC

towelguy wrote: post #101

throwawayaway wrote: post #39

Earlier quoted context omitted.

https://github.com/torvalds/subsurface pretty interesting! the .c's heavily outnumber the .cpp's. there's nothing like having your prejudices confirmed to harden them, so I question whether he is more welcoming.

There's a video about it https://www.youtube.com/watch?v=ON0A1dsQOV0 Apparently, Qt takes away most of the problems they have with C++

Post by netheril96 » Wed, Dec 10, 2014, 3:18 AM UTC

npalli wrote: post #91

mikeash wrote: post #40

A major problem with C++ is a lack of consistency, which you run into if you start trying to generalize the ideas presented in this article. The article demonstrates string concatenation using +. That is great! Except it's inconsistent. The article's example works fine, of course: return name+'@'+domain; I'll skip over the weird use of '' instead of "". Now let's say I want to prepend mailto: as well: return "mailto:…

>>The next example demonstrates initializing a vector: >> vector v = {1,2,3,5,8,13}; >>This is great, of course. The example after that introduces "auto" so you don't have to write the type of a variable. Well heck, let's combine the two! >> auto v = {1,2,3,5,8,13}; The auto example creates an std::initializer_list which then can be converted into a vector or a set std::vector newvectorfromauto(v); std::set newsetfro…

Post by StephanTLavavej » Wed, Dec 10, 2014, 6:52 AM UTC

pierrebai wrote: post #60

mike-cardwell wrote: post #13

"Finally, which version is likely to be the most efficient? Yes, the C++ version, because it does not have to count the argument characters and does not use the free store (dynamic memory) for short argument strings." I just compiled the C code and the C++ code using: gcc -std=c99 -Wall -Wextra test.c -o test g++ -std=c++11 -Wall -Wextra test.cpp -o test According to valgrind: C: total heap usage: 1 allocs, 1 frees,…

This is the archetypal problem with benchmarks: not only are they hard to design, but people will incorrectly nit-pick the results. You count the number of allocations, without looking at the big picture: this is a toy example. It provides the hard-coded input to the function. This results in the C version not having to allocate memory for the hard-coded literals and the function problably being inlined and optimized…

Post by coldtea » Wed, Dec 10, 2014, 8:28 AM UTC

throwawayaway wrote: post #119

coldtea wrote: post #111

Earlier quoted context omitted.

> The answer in all cases is C. Starting to sound like a broken record. No, the answer in all cases can also be found in C++, and understood in C++ terms alone. C++ is a SUPERSET of C, not just an arbitrary language + C.

cheers for the broken record warning. i will now abstain from further conversation - i will leave you with this - i don't care to read your answer in case i have to respond and you might have to deal with some more repetition: using the language of sets, the set of C++ minus the set of C, with what is now left: how can you explain the things i have listed?