I cannot speak for Jamie, at whose feet I gladly grovel, but my theory is that it made Webmin and the attendant code more “inclusive” of what might be added to it. Again, my Perl knowledge is pathetic, but that’s my theory.
What Jamie built, for those of you who have taken the time to really consider it, is a monumental achievement and contribution to system administrators all over the world. I’m not “polishing apples” here. I owe countless hours “recovered” through the use of Webmin to the guy.
Michael Peoples (mp4783)
iGEMS COE, Deployment, Engineering, Application Support and Security
Global Service Assurance, M5
AT&T Business Solutions
Office: +1 614-886-0923
Mobile: +1 614-886-0923
Senior Systems Manager
This e-mail and any files transmitted with it are AT&T property, are confidential, and are intended solely for the use of the individual or entity to whom this email is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited."
On Fri, Mar 22, 2013 at 7:48 AM, Emma wasanzy <firstname.lastname@example.org> wrote:
I have noticed that, the webmin API doesnt support the use of strict and warning. Because any time I tried using them, I get so many "Global ...." errors which are related to the API. Why isn't the API using strict?
I'm sure only the webmin developer knows why he did not use strict, however, you can still use it. Just initialize vars you intend on importing thus:
our( %in, %text, %config );
Older Perl did not support the 'our' pragma, but 'vars.'  So keep that in mind if you are using an older Perl.