C# Puzzle of the Week 11-22-2009

[MarkCuering]

---

IMHO, Solving programming in a way like puzzles is a fun way to develop your logical and problem solving abilities and also let someone sharpen his programming skills, knowing from the others what he doesn't know at the time he tried....

[silent-kill]

maybe its just me, but people who will solve this puzzles are people who is trying to boost there EGOs.
i used to do it before, to prove to everyone that i can program but im over that.
maybe it would be nice to actually create topics about real problems that you are trying to solve.
so we can help you solve it.

rather than posting puzzles, which you already know the answer.

thats just my opinion though

[eax]

maybe its just me, but people who will solve this puzzles are people who is trying to boost there EGOs.
i used to do it before, to prove to everyone that i can program but im over that.
maybe it would be nice to actually create topics about real problems that you are trying to solve.
so we can help you solve it.

rather than posting puzzles, which you already know the answer.

thats just my opinion though

Mao gyud.

Problems that are also realistic or that we encounter on our day-day job like error in saving to the SQL.

[tracernet_v2]

is it me or is it that no one wants to answer this question?


IMHO, this should have been posted on codeproject or stackoverflow or any other programming forum... no offense to the TS... I see the want to help other(s, programmers) learn, just think naa forums that suit the thread more... PEACE...

[dodie]

is it me or is it that no one wants to answer this question?

IMHO, real programmers help each other by solving real problems, not puzzles.
I lead my close friends what to solve a specific challenge and do whatever they like. The rest is up to them.

If you ask us for solve something in programming, real problems makes us a real challenge, breeding good programmers.
I'm relating to test the limit of the new learner, rather than trying to expand it's current knowledge. Programming is different.

If you have a screw driver in your hand, of course you know how to use it... and not driving it like a hammer.

[MarkCuering]

Enough guys, we’ve done discussing it coz I was planning to remove the puzzle, but they suggested not to do it. We just finished a lot of topics like the one I posted here…

https://www.istorya.net/forums/progra...interface.html

but they informed me that none of their answers will be posted on this site surrounded by bloody forumers.
Again FYI, majority of us are apparently new to C# language and .NET Framework. That’s why they don’t bother what negative comments you throw, coz our goal is to learn something and not to boast your egos that you can code.

Please refer to my previous post how we started this:

https://www.istorya.net/forums/progra...xperience.html


If you are following properly, you will notice what topic we are currently discussing behind the forum.
I prepare the puzzle for almost 3 hours, and studied my entire week, investigating on this topic alone. During my preparation, I considered those few who are in college, on how they would understand this. The one who was working in industry already asked me a very levelheaded question that I believe he already spotted the right answer.

“Mark, did you examine already the differences between the usages of STATIC in C#? “

He added then, that this is a very common interview question that might help the two college student. Coz in the design phase the use of STATIC is helpful yet amazingly can ruin the entire performance. I know he is almost there, and I know he is thinking about pointers where he use to deallocate in C++ but in C# and .NET programming it’s not possible… but there’s another way to achieve that… So I decided to post it, isn’t this worth to share? By introducing it on a certain problem like this?

You guys pitching me to ask a real problem? Then what do you call this? A problem produced and generated by the compiler can be track… Of course we had a lot of discussion with that most of the time. I can prove that to you, that this is a real world situational problem. That’s why there is a performance tuning in real environment, Compiler does not detect issues regarding performance and memory usage, and computer runs your program base in your instructions. If it is bloated, then we can’t blame books neither the compiler…

If you are that smart, you will treat this problem as a design phase problem where somebody will put a static delegate to call another class method in order to compare but the implementation of static member must be taken carefully and this is not plainly PUZZLE. You guys just showing who you are in real life, behind this forum.

Anyway, as what we had observed, guys who are not into this stuff, exclusively in C#. They are not interested and the WORST side of it they love to bother throwing stones rather than breads. There’s nothing wrong to post this in the first place, this is not meant to touch somebody’s egos that he can code, this is meant for sharing that at the end of the week, people can read and analyze and make use of the knowledge behind this topic… unlike the others who are wannabee geeks here, showing that they have an X experience on this and that, claiming that they completely have it, but if you will closely read on their post several post where they proide answers… my goodness!!! This puzzle is more worth than they’re claiming to be as if they provided the right knowledge and expertise, they are bunch of bullsh*t eaters here who uttered that they were eating grapes and sharing it to others.

I love to delete my post, but I rather let it stay for the sake of those who would like to know the knowledge behind this problem. If you claim to be an expert in your own sh*t then you damn well ought to add something that is related on this problem that might help to solve the problem. but i dont know... stupid people is stupid as it does!

[MarkCuering]

Mark Members As Static

As the "Mark Members As Static" rule states, there is a slight performance gain in using static methods. You do not have to create an object to access them, and as such they are faster to access and consume less memory; they do not require null checking, etc. If a method does not access any instance variables of a class (StaticMethod above), it is a candidate for being marked static.

If you find that you only use the method on instances of the class that are already instantiated, then there is no performance gain for your program to make the method static and this warning should be ignored. Only mark the method static if you find yourself creating an instance of the class, calling the method (one or more times), and then letting the instance be garbage collected without using it for any other purpose.

A cursory reading of the rule gives the impression that you should either mark the method static, or refer to some instance state of the object within the method ("Mark the member as static (or Shared in Visual Basic) or use 'this'/'Me' in the method body, if appropriate."). NEVER alter the logic of your methods to include references to "this" (in C#, "me" in VB) just to satisfy this rule.


Static holder types should be sealed

This rule assumes that a type that contains only static members is not designed to be inherited, because the type does not provide any functionality that can be overridden in a derived type. A type that is not meant to be inherited should be marked with the sealed modifier to prohibit its use as a base type.

25-NOV-2009 9:30 GMT8 I'm tired LOL...