Hi, On 31/08/2012 22:33, Erik Colson wrote:
And why Wx::Perl ??? cpan is all about Perl isn't it ? No need to put Perl in any module namespace
It is just a convention that a few pure Perl CPAN Wx related modules have been called Wx::Perl:: so it was worth pointing that out.
The only rule that I personally would request folks to follow is that it makes life simpler if the Wx:: top level namespace is reserved for modules that wrap C++ classes.
So Wx::MyModule is reserved for something that wraps a C++ class called wxMyModule. wxPerl internals rely on this so that a few C / C++ functions can serve all the wxPerl classes. It makes maintenance and wrapping new classes and wxWidgets versions really quite simple in most cases ( thanks to Mattia ). Given this, there has to a sub-namespace under Wx:: for use by stuff that does not wrap a C / C++ class so Wx::Perl:: seems a natural enough choice.
Wx::Perl:: is already established in use for several modules outside of the main Wx distribution so as it is there it seems reasonable to point folks at it.
I would agree though that if you are producing a whole set of wrappers then "MyFramework::TextCtrl, MyFramework::Button" and the like seem more appropriate.
Cheers Mark
