Re: [wxperl-users] mixing positional and named parameters

[Eric W. <scr...@gm...>]

# from Mattia Barbon
# on Sunday 18 March 2007 04:19 am:

>=A0 The first is "WxPerl"; right name, wrong capitalization. =A0But this
>might be my flawed sense of aesthetics...

Well, it could be wxPerl::*.  I've been using 'WxPerl::*' in the few=20
extensions and convenience modules that I've done thus far for=20
dotReader, but haven't broken any of those into separate dists.

What would be the ideal namespace for extensions?  I guess my sense of=20
aesthetics doesn't like the de-facto Wx::Perl::*.

>=A0 The second is: I suppose I will need to derive all my classes from
>WxPerl::*. =A0

Yep.  The benefit here is maybe that you get to add more methods to=20
those classes from elsewhere.  If we can decide on an "enhancements"=20
namespace, we could conceivably have a whole pile of cooperating mixins=20
available as we figure out how to grow the API.  I'm not certain if=20
much is needed beyond the constructors though, so ponder that=20
accordingly.

  use wxPerl::Constructors;
  use wxPerl::TreeCtrl::FlyingSquirrel;

>Wouldn't it be better if Wx::Perl::Constructors added a=20
>'create' or 'make' (or whatever) method to all wxPerl classes? For
>example:

Hmm, I prefer Something->new(), but I've considered a complete=20
switcharoo on the Wx:: constructors via an import() option.  This=20
would, of course, need to be aware of caller() in order to not disturb=20
the rest of the system (though it would add a level to the call-stack=20
by the time we got to Wx::Button->new(), etc.  I'm thinking the whole=20
scheme will be installed via globs anyway, so where I install them=20
isn't that big of a deal.

=2D-Eric
=2D-=20
Cult: A small, unpopular religion.
Religion: A large, popular cult.
=2D- Unknown
=2D--------------------------------------------------
    http://scratchcomputing.com
=2D--------------------------------------------------