On 10/6/07, David Cantrell <[EMAIL PROTECTED]> wrote:
> Sébastien Aperghis-Tramoni wrote:
> > Also agreeing for the API change. I know I was pondering about using
> > ".." but can't remember why I didn't.
>
> '..' is only meaningful in the Unix/Win32 world. VMS, RISC OS and
> others call it someth
On 10/6/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> On 6 Oct 2007, at 11:46, Sébastien Aperghis-Tramoni wrote:
> >> Would it also do
> >>
> >> use relative [to => 'My::Big::Namespace'] => qw( This That
> >> Munger::Fast Munger::Precise );
> >
> > It can easily do that. The problem is more the n
Dr.Ruud wrote:
Sébastien Aperghis-Tramoni schreef:
package BigApp::Report;
These would also be nice:
package BigApp::__FROMFILE__;
package BigApp::__FROMFILE__($RCSfile);
Not sure how this is supposed to work, but I think this is beyond the
aim of relative.pm
--
Sébastien A
A. Pagaltzis wrote:
* Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]> [2007-10-06 20:30]:
As a side note, using find(1) on a mini-CPAN and Google
CodeSearch, I only found 3 modules named "tp.pm":
Don’t forget the darkPAN though.
On a side note, if some people here know Perl modules outside C
David Cantrell wrote:
Also agreeing for the API change. I know I was pondering about using
".." but can't remember why I didn't.
'..' is only meaningful in the Unix/Win32 world. VMS, RISC OS and
others call it something else. On the other hand, I think it's
safe to
assume that anyone usin
Ken Williams wrote:
If there were a return value from import(), they could do something
like this instead:
package BigApp::Report;
use relative;
my $Pub = import relative to_self => qw(Create Publish);
my $p = $Pub->new;
Except that, 1), the API has changed
Hi Sébastien,
* Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]> [2007-10-06 18:55]:
> relative.pm is now available on the CPAN.
nit:
--- relative.pm.orig2007-10-06 22:58:22.0 +0200
+++ relative.pm 2007-10-06 22:58:32.0 +0200
@@ -70 +70 @@
-# loads Enterprise::Framework:Bas
# from A. Pagaltzis
# on Saturday 06 October 2007 13:44:
>Then again, I’d called mine lib::relative. Maybe this one should
>be pkg::relative?
That sounds good.
--Eric
--
We who cut mere stones must always be envisioning cathedrals.
--Quarry worker's creed
---
* Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]> [2007-10-06 20:30]:
> As a side note, using find(1) on a mini-CPAN and Google
> CodeSearch, I only found 3 modules named "tp.pm":
Don’t forget the darkPAN though.
> An acceptable compromise it to write it as C< -to => Root >
That’s what I’d sugges
* Andy Armstrong <[EMAIL PROTECTED]> [2007-10-06 14:00]:
> I always hesitate to suggest Aristotle is mistaken - it's not a common
> occurrence
Heh, thanks, but I am wrong plenty. :-)
> but I really think 'subclass' is wrong.
Yeah, I see the point, and I agree.
But I really think `relative` is
Sébastien Aperghis-Tramoni wrote:
> Hello Aristotle,
>> But I like neither the name nor the interface. How about this:
>>
>> package BigApp::Report;
>> use subclass qw(..::Utils Create Publish);
>> # loads BigApp::Utils, BigApp::Report::Create,
>> BigApp::Report::Publish
>
> "subclass"
On Oct 5, 2007, at 9:04 PM, Sébastien Aperghis-Tramoni wrote:
The interest of such a module would be to ease writing modules
using a big set of sibling modules (in the same hierarchy), and
would also simplify refactoring and renaming.
As of now the user still has to write the whole package
Paul Hoffman wrote:
use relative to => "Enterprise::Framework" => qw(Base Factory);
# loads Enterprise::Framework:Base,
Enterprise::Framework::Factory
Hmm, the last example is equivalent to this:
use relative qw(to Enterprise::Framework Base Factory);
Which might conceivably ca
On Sat, Oct 06, 2007 at 04:53:00PM +0200, S?bastien Aperghis-Tramoni wrote:
> Andy Armstrong wrote:
>
> >>>Would it also do
> >>>
> >>>use relative [to => 'My::Big::Namespace'] => qw( This That
> >>>Munger::Fast Munger::Precise );
> >>
> >>It can easily do that. The problem is more the name. In
Hello,
relative.pm is now available on the CPAN. Thanks to Aristotle and
Andy for their suggestions.
For people who care about this, it even works on Perl 5.004
Forwarded message:
From: PAUSE <[EMAIL PROTECTED]>
Date: 6 octobre 2007 18:39:45 HAEC
To: "Sebastien Aperghis-Tramoni" <[EMAIL P
We're thinking about promoting one of the Perl::Critic::More policies
to the core Perl::Critic distribution. As long as the version number
increases and PAUSE permissions are OK that should be fine, right?
http://search.cpan.org/perldoc?
Perl::Critic::Policy::ValuesAndExpressions::Prohibi
Sébastien Aperghis-Tramoni schreef:
> package BigApp::Report;
These would also be nice:
package BigApp::__FROMFILE__;
package BigApp::__FROMFILE__($RCSfile);
--
Affijn, Ruud
"Gewoon is een tijger."
On 6 Oct 2007, at 15:53, Sébastien Aperghis-Tramoni wrote:
Heh, thanks. I'll announce here when the module is available.
Cool :)
--
Andy Armstrong, Hexten
On 10/6/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> I always hesitate to suggest Aristotle is mistaken - it's not a
> common occurrence - but I really think 'subclass' is wrong. As you
> said this is an extension to the semantics of use that has (I
> presume) nothing to do with any inheritance
Andy Armstrong wrote:
Would it also do
use relative [to => 'My::Big::Namespace'] => qw( This That
Munger::Fast Munger::Precise );
It can easily do that. The problem is more the name. In this case,
"use relative to ..." works well. But in y original example, "use
subclass" works better.
On 6 Oct 2007, at 11:46, Sébastien Aperghis-Tramoni wrote:
Would it also do
use relative [to => 'My::Big::Namespace'] => qw( This That
Munger::Fast Munger::Precise );
It can easily do that. The problem is more the name. In this case,
"use relative to ..." works well. But in y original exam
Andy Armstrong wrote:
But I like neither the name nor the interface. How about this:
package BigApp::Report;
use subclass qw(..::Utils Create Publish);
# loads BigApp::Utils, BigApp::Report::Create,
BigApp::Report::Publish
"subclass" would imply more OO semantic than I'd like, a
On 6 Oct 2007, at 11:17, Sébastien Aperghis-Tramoni wrote:
I like the idea. Catalyst privately invents something like that,
so obviously there are other people who feel the same need.
Yes, POE also provide a similar mechanism, that's why I was
thinking to provide a generic module to do that.
Hello Aristotle,
A. Pagaltzis wrote:
Hi Sébastien,
* Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]> [2007-10-06 03:05]:
package BigApp::Report;
use relative to_parent => qw(Utils);
# loads BigApp::Utils
use relative to_self => qw(Create Publish);
# lo
24 matches
Mail list logo