verysunnyday
New Member
- Joined
- Mar 7, 2022
- Messages
- 3
- Office Version
- 2019
- Platform
- Windows
There are lots of information on the internet relating to object oriented coding.
However, they tend to focus on languages such as Java and C++, the reason being VBA does not have Inheritance and Polymorphism, at least not exactly like those found in the aforementioned languages.
What annoys me most is the material provided tends to say words to the effect that classes are only good for large applications.
Every application must start of small, then grows, so surely one shouldn't start writing VBA in a procedural way, then migrate to oo only when it reaches a certain size.
I think to drive the point home, what would be good is to show a VBA application written in both styles ie procedural and oo, then explain why the latter might be more beneficial.
Can someone please provide such an example?
Thanks
However, they tend to focus on languages such as Java and C++, the reason being VBA does not have Inheritance and Polymorphism, at least not exactly like those found in the aforementioned languages.
What annoys me most is the material provided tends to say words to the effect that classes are only good for large applications.
Every application must start of small, then grows, so surely one shouldn't start writing VBA in a procedural way, then migrate to oo only when it reaches a certain size.
I think to drive the point home, what would be good is to show a VBA application written in both styles ie procedural and oo, then explain why the latter might be more beneficial.
Can someone please provide such an example?
Thanks