Class Inheritance: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 6: | Line 6: | ||
*the difference between config tree declarations vs their bodies | *the difference between config tree declarations vs their bodies | ||
*what class blah{}; actually does (vs blah:blah{}) and how to implement it properly | *what class blah{}; actually does (vs blah:blah{}) and how to implement it properly | ||
*how ofp behaves differently in class trees and what access= is all about | |||
--------- | --------- | ||
Revision as of 02:14, 23 July 2010
this is not ready for prime time.
i am just getting some ideas down on how to explain
- the necessity of requiredaddons= aka the pbo loading order
- the difference between config tree declarations vs their bodies
- what class blah{}; actually does (vs blah:blah{}) and how to implement it properly
- how ofp behaves differently in class trees and what access= is all about
Class Inheritence refers to the way in which classes are superimposed onto each other.
class Base
{
a base class containing (probably) embedded classes class EmbeddedClass { ... }; class InheritedClass:EmbeddedClass { ... };
};
The above is the creation of the class with real values
example
class Vehicles {
class Vehicle{......}; class Car:Vehicle{......}; class Truck:Car{......};
};
Inheritence skeleton
The engine needs to know how above is constructed when inheriting from it
if you aren't altering embededded classes:
class Car;
altering things in truck
class Car; class Truck:Car{....};
class anything{}; wipes out previous. NOTE however that reqiored addons is needed