At 06:29 AM 8/19/2009, Chas. Owens wrote:
On Wed, Aug 19, 2009 at 09:03, Peter Scott wrote:
snip
> The Exporter isn't hard to learn, and Exporter::Simple is even easier and
> prettier. Non O-O procedures should be exported.
snip
That last sentence should read "Non OO procedures should be export
On Wed, Aug 19, 2009 at 09:03, Peter Scott wrote:
snip
> The Exporter isn't hard to learn, and Exporter::Simple is even easier and
> prettier. Non O-O procedures should be exported.
snip
That last sentence should read "Non OO procedures should be exported
on demand." Modules should not import an
On Wednesday 19 August 2009 16:03:01 Peter Scott wrote:
> On Tue, 18 Aug 2009 19:39:29 -0400, Steve Bertrand wrote:
> > While reviewing my POD to ensure that I've been keeping it up-to-date
> > properly, and so that I can still easily understand the API at the
> > documentation level, I've noticed
On Tue, 18 Aug 2009 19:39:29 -0400, Steve Bertrand wrote:
> While reviewing my POD to ensure that I've been keeping it up-to-date
> properly, and so that I can still easily understand the API at the
> documentation level, I've noticed that two of my modules have
> subroutines that only perform glob
Uri Guttman wrote:
> making a basic procedural sub into a class method for no reason
> means you pass useless data (the class name) and ignore it in the
> sub. that to me is a poor API.
Point well taken.
> SB> Besides... I'm at a stage where I'd rather carry on with Perl BCP and
> SB> coding
Steve Bertrand wrote:
> Jenda Krynicky wrote:
>> From: Steve Bertrand
>>> Is it recommended that I stick with the overall style of the project by
>>> making all of the modules object-oriented, or is it better to create
>>> procedural modules when objects are not required?
>> Depends. Not on the
> "SB" == Steve Bertrand writes:
SB> Jenda Krynicky wrote:
>>
>> Use whatever feels more natural to you.
SB> I really think I'll stick with OO for consistency throughout, even if
SB> it's just for the simple purpose of having a consistent
SB> my $self = shift;
SB> ...as the
Jenda Krynicky wrote:
> From: Steve Bertrand
>> My ISP management project which started out as a learning experience has
>> grown into a system that currently contains 10 modules. The entire
>> system is object-oriented.
>>
>> While reviewing my POD to ensure that I've been keeping it up-to-date
>
From: Steve Bertrand
> My ISP management project which started out as a learning experience has
> grown into a system that currently contains 10 modules. The entire
> system is object-oriented.
>
> While reviewing my POD to ensure that I've been keeping it up-to-date
> properly, and so that I can
My ISP management project which started out as a learning experience has
grown into a system that currently contains 10 modules. The entire
system is object-oriented.
While reviewing my POD to ensure that I've been keeping it up-to-date
properly, and so that I can still easily understand the API a
10 matches
Mail list logo
