|The stupid question is the question not asked|
Make Perl an OO languageby gildir (Pilgrim)
|on Oct 29, 2002 at 16:57 UTC||Need Help??|
I came to the monastery gates after some time in the wild and I was quite suprised. I found the giant's "learning java?" meditation and wonderd why a perl monk should stick to Java to learn object oriented (OO) programming.
And then I realized that it may be the case, that a perl monk is not pushed to a OO perinciples while programming in Perl and that a humble monk may spend all his life coding (un)structured script ...
And as soon as I realized this, I wanted to cry out "Make Perl an OO Languge". It may sound ridiculous because Perl has OO features, it has classes, methods, inheritance and all that fancy OO stuff ... but it has a lack of OO programmers and OO designers.
When I started to write applications in Perl, I started to write them in a good OO manner as I was taught to do in C++. Latter, when I started to write Java code, I discovered Java to be such a limeted, non-expesive language and I wondered why is Java so popular. Now I understand why it is so and why Java is now a good example of OO approach and Perl is still a 'glue scripting language'. One of the reasons(*) is that Java forces developers to learn OO principles just before they start to write their first 'HelloWorld.java' masterpiece ...
(*) Other reasons can be found here: Order in Perl chaos?
On the other hand, a perl geek is not pushed to OO, it may never learn what a class is in all his life. That may be an advantage as well as disadvantage. While sticking to the TIMTOWTDI principle, I deem it an advantage. But ... a good deal of evangelism is needed to 'pull' developers to the OOP world.
So, my dear perl monks, please, have a look at perltoot and start to write an Object Oriented code today. It will help you to increase your value and it will help perl as well.
And no monk will be pushed to the Java world just to learn OO .....