Class Inheritance: Difference between revisions
Jump to navigation
Jump to search
(Improved formatting.) |
m (Added category.) |
||
Line 52: | Line 52: | ||
class anything{}; wipes out previous. NOTE however that requiredAddons is needed | class anything{}; wipes out previous. NOTE however that requiredAddons is needed | ||
[[Category:ArmA: Addon Configuration]] |
Revision as of 18:13, 11 November 2011
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 Inheritance 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{......}; };
Inheritance skeleton
The engine needs to know how above is constructed when inheriting from it
if you aren't altering embedded classes:
class Car;
altering things in truck
class Car; class Truck:Car{....};
class anything{}; wipes out previous. NOTE however that requiredAddons is needed