Thread: How rude!!

The book is huge so i dont wanna go quote hunting, but the author is persistent on using C and the context as far as i remember is something like "Do it in C++ so you practice OOP"

who does he not write the whole book in C++ ??

The irony of it is that in the end of the book he talks a little about C++ and recommends a book by one his friends

So you think a better advise was not to mention C++ at all? Or to put it in another way, you don't think a C programmer would benefit from knowledge in C++? I can't think of a more powerful combo. It's a match made in heaven.

But hey, don't let the possibility of becoming a great programmer get in the way of your faith.

Originally Posted by Mario F.

So you think a better advise was not to mention C++ at all? Or to put it in another way, you don't think a C programmer would benefit from knowledge in C++? I can't think of a more powerful combo. It's a match made in heaven.

But hey, don't let the possibility of becoming a great programmer get in the way of your faith.

that is not my point, my point is why not use C++ straight up ?

Update: in one point in the book, while explaininig trees, he said something like: "it is a good practice to nullify the 'next' point once the holder object is created. This could be accomplished by using classes and doing that in the constructor"

!!!!!

Again: Just use C++ for Bjarne's sake!!

Originally Posted by Hussain Hani

that is not my point, my point is why not use C++ straight up ?

Update: in one point in the book, while explaininig trees, he said something like: "it is a good practice to nullify the 'next' point once the holder object is created. This could be accomplished by using classes and doing that in the constructor"

But that's good knowledge, Hussain. You gained knowledge of the construct particulars in C and was also given the equivalent in C++. You win.

Look, what I'm trying to transmit is that it really needs to be debunked this general notion that there is anything in a programming language that should be the subject of a Following. A programming language is only a tool. It's nothing more. It's a sad little pathetic tool and you've got the power over it. Not the other way around. Just use it as such and do your whole best to avoid falling prey to all the zealotry surrounding programming languages.

And since you are reading about games, I'll give you a surprising example:

I mentioned this game briefly on another thread on an entirely different context, but have you heard of Solium Infernum? It's a strategy game for up to six players in the best tradition of board games. It's an indie game. It's also a genial game, so well devised I'm still at awe. It's brilliant in the way it gives players a nearly unlimited level of strategic thinking. It's the best strategy game I've played in a decade. You can tell I like it. You may not like it. It's irrelevant mine and your position. What is relevant is that many people like it, I have no shortage of fellow players to pitch my mind against 4 months after release and the author is pleased with the sales. And there no indication anyone will get bored of it soon. At 30 USD, it already payed itself numerous times. Also the artwork is amazing and there's plenty of well written flavor text for every infernal legion, artifact and relic to entertain yourself. The game is here.

Do you know what tool was used to develop this game? Macromedia Director.

I suggest you take a breath, flip the switch in your brain that is telling you to read this book as a bible to C and instead try to understand what the author is doing is giving you knowledge. The little I know of that book (I confess never have reading it) and what I do know from the author, tells me you will gain a lot more from doing this. If you can't do it, or still insist this is rude of the author to do, I suggest you choose another profession. Civil construction is well payed (better than programming these days) and you will never defend framing hammers are better than claw hammers.

Originally Posted by Mario F.

What's the context of that quote?

"As your next assignment in section 3.4.2, try rewriting this game using classes..."