Ok. Let me see if I'm understanding the needs. First off, a pet peeve of mine, "less important" should never be used as a synonym for "simple example"; it is these "simple examples" that let us generize into functionality. Pet peeve aside, let's continue.
1) If you wanted to call Rectangle_area via a call to RectangleStorage_area - without creating a RectangleStorage_area function, this can't be done. The easy fix is to create a RectangleStorage_area function which calls Rectangle_area. The two functions MUST have the same parameters, and any ByRef parameters would need to be the same. You can, however, use different default values, and reorder any parameters - just pass them in the correct order when calling the base class' (rectangle's) function. For consistency though, it would make more sense to preserve order.
Ex.
Code:
BaseClass_someFunction(BaseClassObject, arg1, ByRef arg2, arg3, arg4 = 0)
You would have this for the subclass. All mandatory (non-optional) MUST have values passed, but they need not be args. Ex.
Code:
SubClass_someFunction(SubClassObject, arg1, ByRef arg2)
{
;"5" is passed as arg3, and arg4 will use the default value (0)
return BaseClass_someFunction(SubClassObject, arg1, arg2, "5")
}
2) To inherit values: Store the base classes built-in values first, then add any you want - remember to update the built-in size. Because there is no type checking, Rectangle_getHeight will return the "b1b" member - 1st word, 2nd byte, and return a UShort value - regardless of the object's Class. If you make sure that RectangleStorage sets the height in the same place, you can call Rectangle_getHeight on a RectangleStorage object, and return the height. To call RectangleStorage_getHeight, use the method from (1) to create such a function.
This seems like the easiest way, because I'm still not sure what behavior you need. If you are thinking to allow calling RectangleStorage_getHeight and it calls Rectangle_getHeight, you need to create such a function.
My suggestion for inheritence would be: make a copy of the base class' AHK file, remane it the the subclass, and add to it - that's inheritence. Change the function names to the new class name, and add your own values and functions to it. This allows use of the built-in functions and values of the base class in your subclass. As far as user-defined values, they would have to copy the functionality they wanted. The benefit is that value "1" (first user-defined value) works for the base class and the subclass - provided you set the correct built-in size for your subclass; likewise, since the base class values appear in the subclass (in the same position), you can call the base class methods with a subclass object and it will work fine. Problems exist, though, calling user-defined functions in the base class using a subclass object (if those values are not defined in the subclass).
As an example, color is the first user-defined value for Rectangle. If a user wanted to set the color for a RectangleStorage object, they could copy this function, change the name, and it would work as expected. Calling Rectangle_setColor OR RectangleStorage_setColor would do the same thing. Also, passing a Rectangle to either would work the same as well, since it uses the built-in size to know where the first user-defined value is (i.e the offset).
So, "inheritence" may not be needed, unless you have some need that isn't met by this solution. Now, "virtual functions" (as called in C++, at least), might be useful. For example, calling Rectangle_setHeight and passing a RectangleStorage object would be fine, and work. But for the Shape_draw example function and passing a Circle object, it might be desired to call Circle_draw (if it exists), instead.
_________________
As always, if you have any further questions, don't hesitate to ask.
Add OOP to your scripts via the
Class Library. Check out
my scripts.
Login
Register
FAQ
Search
