Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace #8

Open
saiftynet opened this issue Apr 25, 2018 · 2 comments
Open

Namespace #8

saiftynet opened this issue Apr 25, 2018 · 2 comments

Comments

@saiftynet
Copy link
Owner

It is clear that GUIDeFATE as is is pollution the root namespace. I would like to have the modules that GUIDeFATE uses to be on something like GUIDeFATE::GFwx etc. No sure how to do this...

@chanio
Copy link

chanio commented Feb 18, 2019

CPAN's world is all an experience!
But you have started in a simple and interesting way! And with an interesting and exiting idea! Just keep this path.
Today, I have read your article at http://blogs.perl.org/users/saif/2018/05/ducktaping-the-internet-to-the-desktop.html and just downloaded your module.
Just let it mature and become completely multiplatform...
The number of users would make it grow...
For example, I am appending a new GFgtk2.pm that makes you updtate (if you like it) your GUIDeFATE.pm by adding another target... GFgtk2.pm.zip
This is because there is a whole branch of LINUX users that refuse to upgrade to the recently new Gtk3. For memory reasons, etc. For example: Linux-Mint.
By adding this Gtk2 option before the Gtk one, there is no way of missing the 2 after your normal Gtk regex.
I also enjoy the beauty of programming. And by adding these simple lines just before your Gtk3 options you do not even have to change the original regex.
I am not an expert in perl either, and I promise to test all your code later.
But for now, I have tried your calc example and it works like a charm if you add the use lib with the complete real path of your module's lib directory...
Lets hope that I become an expert in using your module with all the examples in your wiki!
You are going to learn a lot about today's work of maintaining a standard module. That should work the same in all platforms. The more complex it grows, the harder it would become to maintain it standard and backwards compatible at any new version.
But the reward is achieving a lot of wisdom, and tricks to become a better programmer.

@saiftynet
Copy link
Owner Author

saiftynet commented Feb 26, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants