I guess each module author has his/her own preferred way
how to get patches and other forms of help.
I have started to work on a series of talks - that I'd probably develop
with a series of blog posts - on how to contribute to and open source
project with heavy focus on Perl projects.
If
module-authors:
Let's say I have a CPAN distribution called Foo:
# Foo.pm
package Foo;
And suppose the distribution includes:
package Foo::Bar;
sub mysub { print hello, world!\n }
I would like callers to be able to import mysub() with a traditional
'use'
Hi David.
How about importing mysub from Foo::Bar to Foo, and let Exporter to deal
with the next step?
package Foo;
use Foo::Bar qw{mysub};
our @EXPORT = qw{ mysub };
should work.
Shmuel.
On 2011/01/16 22:03, David Christensen wrote:
module-authors:
Let's say I have a CPAN
On 11-01-16 03:03 PM, David Christensen wrote:
Bonus question:
use Fooqw( :all );
What is the best way to accomplish the goal?
Fill in @EXPORT and @EXPORT_OK as needed.
# --
# Exports
use base qw( Exporter );
our @EXPORT = qw( );
our
On Sun, Jan 16, 2011 at 5:09 AM, Gabor Szabo szab...@gmail.com wrote:
My objective is getting more people to contribute to CPAN.
I don't necessarily want more modules. I'd prefer to get more people
involved in maintaining and improving the already existing module.
Reactions off the top of my
Shmuel Fomberg wrote:
How about importing mysub from Foo::Bar to Foo, and let Exporter to deal
with the next step?
package Foo;
use Foo::Bar qw{mysub};
our @EXPORT = qw{ mysub };
should work.
I was wondering about that idea, but was doubtful. Let's try it:
2011-01-16 13:47:47
module-authors:
I'm not sure where to ask this question, so please refer me to a better
resource if there is one...
I'm trying to implement a centralized exception generation function, say
myconfess(), that I can use throughout my code. myconfess() will do
some things and then call
