What is the purpose of internal abstract method in a abstract class?

Question

1.00/5 (1 vote)

See more:

What is the purpose of internal abstract method in a abstract class?
why to make an abstract method internal in a abstract class? if we want to restrict abstract class outside the assembly why don't we just make abstract internal class.
Is there any other logic behind it.

Posted 23-Feb-15 2:56am

mahakaal

Add a Solution

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)

Kornfeld Eliyahu Peter · Answer 1 · 2015-02-23T03:15:00

Solution 1

It can be useful when you want to create a single abstract but want it to be different from inside your code or from code of a 3rd party user...
Like enabling the overriding of a specific method from your own code, but do not for a user of your library...
One sample I had is with Telerik's controls, where the method to render the client side JavaScript was defined as internal...So between controls of Telerik it was overrided, but me, as an end-user it was hidden...(I believe the reason is not let you mess their controls)

Posted 23-Feb-15 3:15am

Kornfeld Eliyahu Peter

Comments

Sergey Alexandrovich Kryukov 23-Feb-15 9:48am

What 3rd-party user? From the same assembly? No, it can be only for internal purpose. Can make full sense though. I'll answer...
—SA

Kornfeld Eliyahu Peter 23-Feb-15 9:50am

3rd-party user - I meant someone (a developer) from the outside who uses your classes/library...

Sergey Alexandrovich Kryukov 23-Feb-15 9:57am

That's the point. Such user cannot override this method, as it is marked internal. Please see my answer; I explained why there is no a controversy.
—SA

Kornfeld Eliyahu Peter 23-Feb-15 10:03am

I didn't try to tell that there is any controversy...I tried to show a sample of how it can be useful...

Sergey Alexandrovich Kryukov 23-Feb-15 10:16am

No, you did not understand me. It's the nature of the inquirer's question, not your post. The inquirer sees some not really existing controversy. Perhaps you answer is just unclear...
—SA

Kornfeld Eliyahu Peter 23-Feb-15 10:19am

I see... I will try to improve it... Thank you...

mahakaal 23-Feb-15 23:23pm

if i marks any method internal in abstract class, we can't override even a single method of that abstract class outside the assembly...

Sergey Alexandrovich Kryukov 23-Feb-15 23:45pm

Who told you so? How about thinking a bit, not just making a statement? (False statement, anyway.)
First of all, who told you that for using some class (event outside of the declaring assembly) you need to override it there?

Listen, the logic is simple as a sledge hummer. You just need to grasp it, slowly, step by step. You are doing wrong assumption. Try not to do any assumptions, and probably you will see you mistake. (Really, really trivial mistake, frankly.)

—SA

mahakaal 23-Feb-15 23:19pm

am not clear about it yet.
if making an abstract class internal can restrict it's access from outside the assembly than what is the purpose of making it's abstract method internal.

what are benefits in both context...

Sergey Alexandrovich Kryukov · Answer 2 · 2015-02-23T03:56:00

If you are really talking about internal abstract method, it does not tell us anything about the class's access modifier, so it can be either internal or public, and the inner class can also be private, which is equivalent to internal, but limiting the scope to that class's declaring class.

If the class itself is also internal, I hope you won't see any controversies. Let's assume that you see the controversies when this class is public. But such controversies are purely imaginable, perhaps because you assume too much. If you thought that some abstract method has to overridden in some code outside of the assembly, you would assume too much, missing apparent logic. Who would tell you so? Of course, an abstract method only makes sense when it is eventually overridden, but why it or all overridden versions should be accessible outside the assembly. The whole set of all those methods could be just a part of implementation detail, not directly accessible by the users of this public class. The "mystery" is in fact more than trivial. (Of course if the code you review is reasonable.)

—SA