When making libraries available for VL you sometimes need to inherit from a base class. In order to do so can we just start with a reduced feature set like so:
ability to list a class in the supertypes
ability to overwrite virtual or abstract methods / operations by just adding them to the list of operations (they then grab the signature of the base class regarding their inputs and outputs)
overriding a certain overload with a certain signature. Can we assume that the name of the operation is enough to find the method that shall be overridden?
open questions:
how to treat virtual or abstract properties? We don't have actual .Net properties. We only have setters and getters = patterns on how to name operations and we have fields.
how does that relate to the proxy system? Can we disable it for those types if it becomes an obstacle?
Quest #11
When making libraries available for VL you sometimes need to inherit from a base class. In order to do so can we just start with a reduced feature set like so:
we skip:
open questions: