There's nothing wrong with it, it just seems a bit too discursive for me.
If you don't like something, that simply means you don't like it. It does not mean there's anything wrong with it.
They are people. But that doesn't mean they like the same things as you do. People are different, accept that.
Last edited by maxorator; 04-18-2008 at 05:08 AM.
"The Internet treats censorship as damage and routes around it." - John Gilmore
actually in my case too, i did not say it was wrong, i asked why it is better, and i just explained that i could not justify it.
i accept that.They are people. But that doesn't mean they like the same things as you do. People are different, accept that.
also even if they like the same thing as i do, they still may not like to share it with me anyway, since, for the most of it, they came to this board for an entirely different purpose!
and about the coding styles, it's better that, i stop saying anything!
In this context - recycle: v. to use again.
You shouldn't manav. Just ignore him. Don't be afraid to ask anything even if some people in here are currently thinking too much of themselves to take the time and lay down an answer that doesn't involve calling you an ignorant.
They are just forgetting that a little while ago they were the ones doing the questions and, more often than not, just like you, they didn't understand enough of the programming language to judge the relative value of these questions.
Personally, the simple fact you are worried with coding styles, the presentational aspects of your code, and basic coding strategies, reveals to me you are in the right path. Ask away and try to filter what good answers you get and just ignore the rest of the self conceited noise. (An advise I not always follow, but wish I did.)
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
"The Internet treats censorship as damage and routes around it." - John Gilmore
There is of course a balance to be struck between making tiny functions that do almost nothing but call another function, and a huge function with thousands of lines in it. Functions should do something - not necessarily that much either, but there should be some work other than just calling another function [in most cases].
In C++ you often find that a class calls a function in another class, which calls a function in another class, and so on. If all levels of calls here "do nothing but call the next level", one must ask if all these class levels are needed.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.