int *ptr = NULL;412 karma · joined February 17, 2008
int *ptr = NULL;This was in 1999, I think.
Speaking as someone who's spent the last 6 years maintaining large C++ applications, I'd like to think that any C++ bashing I indulged in was at least informed C++ bashing... ;)
How do you suppose memory management works in high-level languages? Magic?
That's something I've never found to be the case. Most of my C functions are 5-15 lines long. Anything more than 20 lines long is a candidate for refactoring - the unit tests will tell you if you've broken anything.
People choose C over C++ because C is a simpler language than C++, something which this new standard does nothing to address.
Secondly, you are at liberty to write code in your free time, where you can experiment with whatever language/IDE/OS combinations you deem fit. I'd argue this will also make you a better programmer.
"Structure is _nothing_ if it is all you got. Skeletons _spook_ people if they try to walk around on their own. I really wonder why XML does not."
To put it another way, if you have a literal zero in a pointer context, the compiler will replace it with the machine's representation of a null pointer, which may or may not be a machine word with all bits zero.
I think that's right...
That would be when someone makes a generalization. I'd suggest that it's always dangerous to generalize when talking about people's lifestyles and habits.
But it's probably a bad idea to have a nuclear reactor in an earthquake zone anyway, regardless of whether it's underground or not.
Not to devalue the doctor's work though. He did save someone's life.
More seriously, I have been known to spend weeks thinking about the code I'm about to write, but I only really think about the general form and structure of the code. I don't really get too into issues of the precise syntax until I start actually "putting it into the editor".
("What do you mean, you can't open 2 files with the same name? They're in different folders! For the love of God, why?!")
How surprising... ;)
Focus first on playing all the notes in the right order. Don't worry about the timing at all, even if it takes several seconds to move from one note to the next. Once you can play all the notes, then you start to work on the timing, playing gradually faster and faster until you have both the melody and the rhythm mastered.
The idea is that once you have memorized the correct movements, it's much easier to work on the timing. If you start playing too fast and make mistakes, you'll start to memorize the mistakes.
http://www.jsoftware.com/jwiki/Studio/IdiosyncraticIntroduct...