141–150 of 231 posts
Even if you're an experienced programmer or have no interest in C++ you should still read this book.
It's one of the best examples of technical writing and teaching computer programming that I'm aware of.
Earlier quoted context omitted.
Conversely, We write code once, but read it many times, so longer names seems like a poor efficiency choice.
What's the logic of that though? Longer more descriptive names (self-documenting code) help readability, not hinder it. Certainly time to enter code (which is increasingly going to be automated) should be the last consideration - if we're considering full software lifecycle then coding probably takes up some small single-digit percentage of the time we're interacting with the code.
#include
#include
#include
#include
#include
#include
#include
Earlier quoted context omitted.
Rust is cool now. Python is not cool anymore.
I think Python fell victim to the Peter Principle. It got promoted beyond its competence.
Some that come to my mind: its versatility binding native code and its easy-to-fit in your brain mental model for many tasks. The fact that you can script with Python without a compilation step also helped a lot to spread its popularity I think.
Earlier quoted context omitted.
Already teaching you about the maintainability of tightly coupling different parts of your system before you've even opened the book
It would have been awesome if that ISBN issue were an actual ISBN re-use issue. I've run into issues coupling my system's design to the assumption that ISBNs uniquely identify a single edition of a single book. The intent of ISBNs are to be unique, but mistakes are made and resellers lose track or straight up abuse some ISBNs.
Why does Bjarne only sometimes use a space after #include ? #include #include #include #include #include #include #include https://www.stroustrup.com/PPPheaders.h
Any recommendations?
Earlier quoted context omitted.
Yep, although I do like not having clashing names. But I mean... somehow every other language solved this.
> But I mean... somehow every other language solved this. Did they? C, Lisp, Rust, Python, Ada, Go, Java, C#, ... They all require you to qualify conflicting names if some other characteristics (for instance the number or types of arguments) don't provide enough information, or outright don't permit it (C, since it has no notion of name spaces). Can you point to the "every other language[s]" which have solved this pr…
Know what I like about Stroustrup's code? "using namespace std;". The typical convention of sticking std:: in front of std::every std::last std::bloody std::thing drives me std::insane.
You learned to program on Windows, didn't you?
BeOS probably had the nicest looking API. Let's hear it for is_computer_on_fire()
Earlier quoted context omitted.
Same for me. Mainly due to the packaging fiasco (and to a lesser extent, imports). The actual language is not awful. Some features are even nice, like infinite precision integers by default, and separate / and // operators. Language is ok. Setting everything up is atrocious. The other quite annoying thing is that the docs are extremely badly organised so Google rarely points you directly at what you want. Instead you…
Pixi.sh has been great for me so far, it’s a single binary install that can install Python, conda packages and PyPi packages, maybe give it try!
Python needs an official solution.