How to prevent method overloading

Question

1.00/5 (1 vote)

See more:

Hello ,

I dont know whether this question is right or wrong, but i was just asked that how can i prevent overloading in c#. Any ideas on this?

Posted 24-Aug-15 6:41am

Vishal.KumarSingh

Add a Solution

Comments

Michael_Davies 24-Aug-15 12:50pm

Lots of answers from Google...

[no name] 24-Aug-15 13:51pm

but i am not able to judge which one is right. That's why i posted here for final correct answer.

I dont like this thing on CP. If i post some question here , means a trust that i can get an answer here. I just love this site, but sometimes the comments hurt me..

OriginalGriff 24-Aug-15 14:13pm

The problem is that it's a "big question", stated as a single line.
Which means that it can't be simply answered - any more than you found exactly what you wanted to know with a simple Google.
Yes, Michael is right - Google does have lots of answers. But the real problem is that you haven't stated clearly what you need to know. And if you have had "comments hurt me" before then they are probably responding to questions that are as vague.

Remember, we can't see your screen, access your HDD, or read your mind - we only get to work on exactly what you tell us; we get no other context to work from. And there are lots of ways to prevent overloading - but we don;t know what kind of situation your homework wants you to think in terms of.

So take a step back and try to think about the problem from someone who knows nothing about what you are trying to do but who may well know the answer if you ask the right question.
One example I do tend to give is "explain it like you are talking to your mother on the phone" - because if she can't understand what chance do we have? :laugh:

Michael_Davies 24-Aug-15 14:15pm

Do not use Virtual or Override seems to be the answer, maybe the use of Sealed.

https://msdn.microsoft.com/en-us/library/aa645769(v=vs.71).aspx

Sometimes the questions hurt ...

Philippe Mori 24-Aug-15 14:15pm

If someone say to Google the answer, it is usually because they tried it and found a lot of answer.

Maciej Los 24-Aug-15 14:15pm

https://msdn.microsoft.com/en-us/library/aa645769%28v=vs.71%29.aspx

Sergey Alexandrovich Kryukov 24-Aug-15 14:15pm

I wonder where did you see it? How "overloading" can be prevented at all? It's similar to the "requirement" of "preventing letter 'A' in method names". :-)
—SA

Henrik Jonsson 24-Aug-15 14:13pm

Do you really mean mean "overloading", as in having the same method name but with different parameters, and not "overriding", meaning that a derived class creates a new version of the method with the same parameters. For the latter, overriding, you can use the "sealed" keyword. For the former, overloading, it is not possible without using a static code analyzer (written using Roslyn for instance), or a tool that uses reflection on the compiled assembly to look for methods with same names but different signature (parameters).

Try to explain what you want to prevent, and reason for it. Then maybe someone can help you better.

Sergey Alexandrovich Kryukov 24-Aug-15 14:19pm

Good points. However, I mentioned the possibility of overriding in my answer already, before you posted that comment, please see. I also tried to explain why "preventing overloading" cannot make sense. Yes, you have a good point of using static code analysis (which everyone could write, for such simple cases), but it would be totally pointless from a practical point of view. This is the same as trying to limit some useful functionality of a language and .NET.
—SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Accepted Answer · 2015-08-24T08:29:00

Solution 2

In addition to solution 1 by Sergey Alexandrovich Kryukov[^], i'd suggest to read this: CA1402: Avoid overloads in COM visible interfaces[^]. It might help you to understand what Sergey wanted to tell you.

In a short: you have to go back to basics and read about inheritance[^], polimorphism[^], member overloading[^], etc.

Posted 24-Aug-15 8:29am

Maciej Los

Comments

Sergey Alexandrovich Kryukov 24-Aug-15 14:48pm

5ed.
—SA

Maciej Los 24-Aug-15 15:27pm

Thank you, Sergey.

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-08-24T08:12:00

Solution 1

You cannot prevent "overloading" by one simple reason: there is nothing to "prevent". It's not a mechanism or anything special, it's just the rule for naming: you can use the same names for different methods provided that it's possible to resolve which method is to be called by the set of parameters. If some name is allowed, you cannot make it prohibited.

(Perhaps you messed up the terminology and meant to say "prevent overriding". Then, on the level of class, you could use sealed.)

—SA

Posted 24-Aug-15 8:12am

Sergey Alexandrovich Kryukov

Updated 24-Aug-15 8:14am

v2

Comments

Maciej Los 24-Aug-15 14:23pm

Override, overload seems to be similar ;)
5ed!

Sergey Alexandrovich Kryukov 24-Aug-15 14:24pm

Thank you, Maciej.

The similarity of those words (not notions, of course) confused so many developers/students, so I consider the "term" "overload" (but not "override") as one of the worst computing terms in history. In fact, there is no any need for this term (well, maybe "operator overloading" still could be used, but I wish we had a better term). Just allowing to use the same method id does not need any term at all. The language manual can just state that it's not prohibited, without making much buzz about it ("Much Ado About Nothing"). But some explanation of compile-time errors in cases when the resolution of the method is not possible would be still needed.

—SA

Maciej Los 24-Aug-15 15:32pm

I though i understand these terms... but still i'm not sure i'm gettting of English.