Skip to main content

Interface Vs Abstract

Interface..
1. A class can implement from many interfaces
2. A class may or may not implement all methods of an interface
3. There can no fields in a interface
4. There can be no access modifiers. By default all methods are public.
5. No default implementation allowed in interface
6. Define peripherial abilities of a class which two different types of sub classes can inherit
7. Performance: codes requires more time to find the actual method in a class
8. Adding new method to base interface class would require finding all classes that implement the interface and implementing new method


Abstract
1. A class can inherit from only one abstract class
2. A class has to implement all methods of an interface
3. Fields are allowed
4. Different access modifiers are allowed.
5. You can provide default implementations
6. Defines core abilities of a class.
7. Performace: fast
8. Adding new method, we can provide a default implementation for all classes in one base abstract class.

A good example can be viewed at http://www.codeproject.com/KB/cs/abstractsvsinterfaces.aspx
Labels:

Comments

Laura Bush said…
Great job for publishing such a nice article. Your article isn’t only useful but it is additionally really informative. Thank you because you have been willing to share information with us. Custom Software Service Provider In Malaysia
17 February 2021 at 22:11
Post a Comment

Popular posts from this blog

Why there is semicolon at the start of a JavaScript function?

Very often while reviewing the code for my team, I will come across a semicolon at the start of JavaScript function as show below ; (function () { 'use strict'; ...and I often wondered what purpose it served. Guess what. It is an insurance to make sure your script works fine when all other scripts are merged together;  The leading ; in front of immediately-invoked function expressions (iffe) is there to prevent errors when appending the file during concatenation to a file containing an expression not properly terminated with a ;. So there you go. Now you know what that little semicolon is doing there in your code.
3 comments
Read more

C# Performance Improvement - The Power of StringBuilder

 Often when we are wring code we don't think about performance and go with the default options available to achieve a task. String concatenation is one such scenario. If you are doing simple and few string catenations, then you can use the following result = string1 + string2; string1+= string2; result = String.Concat(string1,string2); String.Format and string interpolation are few other options.  However when you are performing large and repetitive  operation, string catenation can be expensive. Here is an example to prove the point.  As you can see it took 41 seconds to perform 100k string catenation. Now lets replace this with StringBuilder and see.  8 ms!!!!!! That is a massive performance difference. Hope you get the point. More info on StringBuilder can be found here https://learn.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=net-7.0
Post a Comment
Read more