I wouldn't read ahead if i was you... scenes are much more epic with the bad ass music and color.... but its always awesome to read up in the manga on eps. you've seen, because the miniscule differences will make you happy.
I wouldn't read ahead if i was you... scenes are much more epic with the bad ass music and color.... but its always awesome to read up in the manga on eps. you've seen, because the miniscule differences will make you happy.
I won't read ahead in the manga, because this way it is more exciting. But i'm going to read it afterwards, only there is no time at the moment (exams). But i thought this scene he mentioned already happend in the anime, so i can take a short look.
Sorry for beeing a little bit offtopic
All you programmers:
It's valid code if 1: 'points' is made global or a is reference; or 2: it's not OOP
If it really was OOP then he would have just made and operator overload and then used 'assertionfailure++'
Absolutely not. Never overload operators to do things that arent super-obvious. If you overload an operator only make it do exactly what the operator usually does (for example changing << and >> for cout and cin is generally considered a bad move, and I agree)Originally posted by: oniorochi
If it really was OOP then he would have just made and operator overload and then used 'assertionfailure++'
i disagree, it can be both oop and local.
Score, takes a name(struct) and a point value(int)
and gives that score to the person where each person is a struct w/ many properties ie score, asshattery cofactor, name, IQ etc.
Now, if incrementing ones score is a common operation its useful to have a function that given a name
increments that persons score.
so
Void increment(Struct peep.name name1)
get current score put it into variable called points
call score with name and points++
return nothing
so points is local
its still oop
and the debated function call is valid
Edit: and Kimmamaro rox
When man invented the bicycle he reached the peak of his attainments. Here was a machine of precision and balance for the convenience of man. And (unlike subsequent inventions for man's convenience) the more he used it, the fitter his body became. Here, for once, was a product of man's brain that was entirely beneficial to those who used it, and of no harm or irritation to others. Progress should have stopped when man invented the bicycle. ~Elizabeth West, Hovel in theHills
No, that's not true, you always consider context when programming and thus overloading ++operator is perfect.Originally posted by: Myran
Absolutely not. Never overload operators to do things that arent super-obvious. If you overload an operator only make it do exactly what the operator usually does (for example changing << and >> for cout and cin is generally considered a bad move, and I agree)Originally posted by: oniorochi
If it really was OOP then he would have just made and operator overload and then used 'assertionfailure++'
That's why you should do document driven development. Also, C++ is a shoddy language, a solution looking for a problem that didn't exist.
Anyway, Kimimaro is "so far" not cool at all. We will wait and see, maybe he will not be a completely dead horse.
I want Naruto to stop being a complete retard, he has never been this useless.
[quote]
Originally posted by: oniorochi
[quote]
Originally posted by: Myran
C++ is definately not a shoddy language!Originally posted by: oniorochi
No, that's not true, you always consider context when programming and thus overloading ++operator is perfect.
That's why you should do document driven development. Also, C++ is a shoddy language, a solution looking for a problem that didn't exist.
Anyway, Kimimaro is "so far" not cool at all. We will wait and see, maybe he will not be a completely dead horse.
I want Naruto to stop being a complete retard, he has never been this useless.
Anyway this is really way off topic with all the programming talk.
As for Kimimaro I'm on the side of those who feel, well, disappointed,
"Our hearts are full of memories but not all of them reflect the truth. The heart isn't a recording device. Even important memories change with time. They warp or fade, leaving us with but a shadow of what we hoped to remember." 天の道を行き、全てを司る。これは僕の世界。
If you too had written a compiler you would know what I'm talking about.
"Commonly Used" and "Good" are completely unrelated. Now, Objective-C preceeded it and is what C++ should have been, but it's not needed today either.
Either way, what is the coolest blood line limit so far? Haku's is a good bet, but maybe the 1:st had a limit as well because the "Birth of the Trees"-jutsu could only be used by him, and if it is then I vote that one ;-)
(with "Birth of the Trees" being my favorite jutsu so far)