On Thu, May 28, 2009 at 1:45 AM, Austin Schutz <[email protected]> wrote: > On Mon, 25 May 2009 18:00:12 -0700 > Eric Wilhelm <[email protected]> wrote: > > > # from Jonathan Yu > > # on Monday 25 May 2009: > > > > >I'd like to remove the Qt module from CPAN, or be able to take it > > > over. > > > > Hi Jonathan, > > > > That's a good question in general, but for Qt4, I'm inclined to say > > that a better approach would be to use the 'Qt4::' namespace. > > > > $Qt4::++; > > IMO this would be a much better choice than Qt::. What happens when Qt > version 5 comes out? All the modules using Qt version 4 (even if they > use "require") will break. What happens when Qt v6 comes out? It may > not even be possible to know what version of an API code is trying to > interact with. > > By using Qt4:: a certain amount of automatic future proofing is implied > for the module users. Yes, I'm sure there will be changes between minor > versions, but it shouldn't be anything as drastic as between > Qt3/Qt4/etc. >
That's the approach that GTK 2 Perl bindings took and it is working fine. Take a look at http://search.cpan.org/dist/Gtk2/Gtk2.pm -- Emmanuel
