Maximizing.ASP.dot.NET.Real.World.ObjectOriented.Development [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Maximizing.ASP.dot.NET.Real.World.ObjectOriented.Development [Electronic resources] - نسخه متنی

Jeffrey Putz

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید






Summary


Shifting away from the scripting mindset isn't easy, but it yields many benefits when you take an object-oriented approach to development. In this chapter, we showed how encapsulating common functionality into a class enables us to reuse the same code, while the calling code doesn't need to know anything about its implementation. Whether it is a car object or a customer object, these logical units do something for us. Their functionality is exposed through a number of members that describe the object and make it do things.

A class is the physical code we group together to make an object do its thing. The object is the instantiation, or manifestation, of the underlying code in the class. Classes are compiled and stored in assemblies, available to be called by any other code in our application.

Inheritance enables us to extend and alter an existing class without having to know anything about its underlying logic. This makes adding a feature to a class a piece of cake, removing the need to reinvent the wheel.

In the next chapter, we'll get into the real nuts and bolts of a class.


/ 146