Early Binding


Early Binding And Late Binding.......

if the base class object wants to call the function of derived class ,it will get the reference of base class function at run time since there is association between base class to derived class at compile time. this is late binding..
(
class A{}
class B:A{}
class c:b{}
)
In the above program child class has already known the reference of parent class like we can say that when child has the reference of any parent class then it is earlier known to that child to which class it is derived...
So, Here is Early binding
But Any parent class don't have the reference of any child we have to give it explicitly by some process or mechanism (virtual and abstract keyword) and at run time parent class will take the reference of his child class because pointer mechanism starts at run time not compile-time....
..............................................Topic Starts here.................................................

Early and Late Biding
.........................
if the type of object is deterministic means type of object(class name) is confirm before creation of object and this object allocates memory by new keyword. we can say this object is early bound with confirm type.
If there is a class name employee. we create the object of this class as................
employee ravi=new employee();

here one thing is clear that ravi is of type employee; so we can say ravi is early bounded. we can not assign any other object type to ravi object...
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''.
if the type of object is no-deterministic means type of object is not known before execution of program. the type of object points to a particular class at run time. This process is called late binding since the object takes decision to which class it have to point is determined late(run time).

an object is late bounded when it is assigned to a variable declared to be of type Object. Objects of this type can hold references to any object.

................................................................
if the dll is loaded at compile time by syntax :>csc /t:library prg.cs ,the dll is early bounded to program......
if the dll is loaded at run time by the use of reflection , this is late binding;

Derived class has the the reference of the base class before creation of object of derived class. means derived class is early bounded to base class. so the derived class object can determine at compile time which function has to be called of base class or derived class..

we should use early-bound objects whenever possible, because they allow the compiler to make important optimizations that yield more efficient applications. Early-bound objects are significantly faster than late-bound objects and make your code easier to read and maintain by stating exactly what kind of objects are being used. Another advantage to early binding is that it enables useful features such as automatic code completion. Early binding also reduces the number of run time errors.

Comments

Post a Comment

Popular posts from this blog

SQL SERVER noteS......ip notes....

                                FUNCTION CREATE FUNCTION Addition() RETURNS Decimal(6,3) After specifying the type of value that the function would return, you can create a body for the function. The body of a function starts with the  BEGIN  and ends with the  END  keywords. Here is an example: CREATE FUNCTION Addition() RETURNS Decimal(6,3) BEGIN END Optionally, you can type the  AS  keyword before the  BEGIN  keyword: CREATE FUNCTION Addition() RETURNS Decimal(6,3) AS BEGIN END Between the  BEGIN  and  END  keywords, which is the section that represents the body of the function, you can define the assignment the function must perform. After performing this assignment, just before the  END  keyword, you must specify the value that the function returns. Thi...
Read more

page life cycle in asp.net.......

Image
Asp.net application and pagelifecycle Introduction In this article, we will try to understand what the different events are which take place right from the time the user sends a request, until the time the request is rendered on the browser. So we will first try to understand the two broader steps of an ASP.NET request and then we will move into different events emitted from ‘ HttpHandler ’, ‘ HttpModule ’ and ASP.NET page object. As we move in this event journey, we will try to understand what kind of logic should go in each and every one of these events. This is a small Ebook for all my .NET friends which covers topics like WCF, WPF, WWF, Ajax, Core .NET, SQL, etc. You can download the same from here or else you can catch me on my daily free training here . The Two Step Process From 30,000 feet level, ASP.NET request processing is a 2 step process as shown below. User sends a request to the IIS: ASP.NET creates an environment which can process the request. In other words, it crea...
Read more

ASP.Net Page Life Cycle

Understanding the Pagelife cycle is important to develop ASP.Net application. The general Page Life Cycle Stages are: 1. Page request - Here Page is requested by the user. 2. Start – Sets the properties such as Request, Response, IsPostBack and UICulture. 3. Page initialization - Controls on the page are available and each control's UniqueID property is set. 4. Load – Controls are loaded here if it is a PostBack request. 5. Validation – Sets the IsValid property. 6. Postback Event handling – Event handlers will be called if it is PostBack. 6. Rendering - the page calls the Render method for each control, providing a text writer that writes its output to the OutputStream of the page's Response property. 7. Unload - Unload is called after the page has been fully rendered, sent to the client, and is ready to be discarded. Common life cycle Events: 1. PreInit – Start event of the Page life cycle and here every page controls are initialized. 2. Init – This is used to read or initia...
Read more