On Thu, May 28, 2009 at 1:45 AM, Austin Schutz t...@off.org wrote:
On Mon, 25 May 2009 18:00:12 -0700
Eric Wilhelm enoba...@gmail.com 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,
On Mon, May 25, 2009 at 06:00:12PM -0700, Eric Wilhelm 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
This may solve both of your dilemmas:
http://search.cpan.org/~ovid/aliased-0.22/lib/aliased.pm
:-)
We packaged that for Debian not too long ago.
On Tue, May 26, 2009 at 11:38 AM, Eric Wilhelm enoba...@gmail.com wrote:
Hi Chris,
# from Chris Burel
# on Tuesday 26 May 2009:
One thing I
Hi Chris,
# from Chris Burel
# on Tuesday 26 May 2009:
One thing I thought of doing was calling the module Qt4, but that would
populate the Qt namespace.
That is going to cause you headaches with the PAUSE indexer. It finds
all of your package statements and will flag your dist as
On Tue, May 26, 2009 at 5:05 AM, Peter Pentchev r...@ringlet.net wrote:
Erm... I don't think that the Qt module written in 1997 would
support Qt 3 :)
Actually, from the module's README file:
This release, PerlQt 0.03, is distributed under the LGPL and requires
Qt-1.1 and Perl 5.004
Chris:
I'm not sure if that's the most desirable behaviour, as it differs
from the rest of the Perl world... Also, one useful thing is that if
you want to create an object of something in Perl you could do:
my $foo = Foo::Bar-new();
my $bar = $foo-new();
Which would create a $bar of the same
It also makes it easier to inherit the constructor when subclassing the
module. I would suggest that Perl modules should be done the Perl way,
rather than by importing ideas from other languages.
On Tue, May 26, 2009 at 11:22 AM, Jonathan Yu jonathan.i...@gmail.comwrote:
Chris:
I'm not sure
On Tuesday 26 May 2009 21:22:33 Jonathan Yu wrote:
Chris:
I'm not sure if that's the most desirable behaviour, as it differs
from the rest of the Perl world... Also, one useful thing is that if
you want to create an object of something in Perl you could do:
my $foo = Foo::Bar-new();
my
--As of May 26, 2009 12:33:08 PM -0700, Bill Ward is alleged to have said:
How would you feel about ref($foo)-new();
--As for the rest, it is mine.
As a clone? Off the top of my head, I can't see what's that doing. A bit
of thinking (and reading) about ref() makes it understandable, if
On Tue, May 26, 2009 at 2:59 PM, Hans Dieter Pearcey
hdp.perl.module-auth...@weftsoar.net wrote:
On Tue, May 26, 2009 at 05:56:10PM -0400, Daniel Staal wrote:
--As of May 26, 2009 12:33:08 PM -0700, Bill Ward is alleged to have
said:
How would you feel about ref($foo)-new();
--As for
On Mon, May 25, 2009 at 6:00 PM, Eric Wilhelm enoba...@gmail.com 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
And really, what's wrong with Qt4::Application-new()?
I've been modeling the Qt4 bindings off the Qt3 ones that Ashley and
Germain wrote. And that's how it works in 3, so I kept it.
No,
Check out this document from Germain Garand wrote for PerlQt3:
http://web.mit.edu/perlqt_v3.009/www/index.html#anatomy_of_perlqt
Syntax elements summary :
1. All Qt classes are accessed through the prefix Qt::, which
replaces the initial Q of Qt classes. When browsing the Qt
documentation,
# 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.
I'm working with someone else on
14 matches
Mail list logo
