# from Bill Ward on Thursday 12 September 2013:
On Thu, Sep 12, 2013 at 8:56 PM, Greg Lindahl lind...@pbm.com wrote:
Vehicle:: doesn't generalize very well to toasters, refrigerators,
etc. If a new top-level name is a good idea, I'd suggest an
Internet-of-Things top-level, Thing:: or IoT:: or
# from Chris Marshall on Friday 30 August 2013:
I've made two email attempts to the module author
and tried to reach him by phone without luck.
Hi Chris,
I hope you are not using that fotango.com address -- that company is
closed. Maybe Artur's @cpan.org address is not updated? Did you try
# from Linda W on Saturday 16 March 2013:
With the discussion I read at the link above, they were more concerned
about changing the version number in one place for multiple
files. Related issue, but
likely different. Certainly we could all play games with specialized
perl scripts that search for
# from Gabor Szabo on Friday 01 March 2013:
I don't maintain my MANIFEST file manually, but have a MANIFEST.SKIP
file and run make manifest before the releases.
As the MYMETA files are new, they were not matched by any of the rules
in the MANFEST.SKIP file.
Oh, that's why I didn't see this. If
# from Gabor Szabo on Thursday 28 February 2013:
/me is releasing new version of Test::Strict to fix this issue and
going over the
other modules as well.
Hi Gabor,
How did they get into your MANIFEST in this case? Is there a tool which
is tending to do this, or are people adding them manually?
# from Linda W on Friday 01 March 2013:
They worked when I ran them in the 't' directory.
...
When I ran it in 't' , the mod was in ../lib... but not under the
test harness?
Hi Linda,
Probably chdir .. and try the tests as t/foo.t -- this will be more like
what you'll see from `./Build test`
# from Aaron Trevena on Friday 01 March 2013:
A quick google search shows it in one of my modules blush and github
shows I added it manually and deliberately like an idjit.
Thanks for the input. I tend to `MANIFEST; ./Build manifest` and have
a check for that in my publish script. I'm curious
# from David Cantrell on Tuesday 06 November 2012:
So how would I fix the dependency problem if I don't even know about
it?
By testing your code before releasing it? ... For the few of my dists
that I care most about,I re-test them every so often to make sure that
CPAN didn't break them.
The
Hi Josh,
# from Joshua Megerman on Friday 14 September 2012:
My initial inclination was to just call the
module WMIClient, but I'm starting to think that WMI::Client or some
other name would be better. The only 2 modules I currently see on
CPAN that provide similar functionality are DBD::WMI and
# from Pedro Melo on Friday 07 September 2012:
... personal modules that don't fit into any other namespace, for
public experimental modules, and for author metadata.
...
You can skip indexing them on search/metacpan, or index them and not
include them on general search results. Make that opt-in.
# from Linda W
# on Monday 28 November 2011 10:07:
In that case, such modules on CPAN are worse than DEAD WEIGHT, they
don't just take up space. People, like you say, come to CPAN for
'modules that install in a straight forward manner'. If the module
fails in that regard, then the module
# from Leon Timmermans
# on Tuesday 18 October 2011 00:37:
I've been pondering the same. For parts of the codebase that don't use
much dynamic module loading it may be possible to automatize this
using Perl::PrereqScanner. I think we could actually use some
clustering algorithm after that (irony
# from Aristotle Pagaltzis
# on Sunday 28 August 2011 22:50:
In my understanding, the complexity of Module::Build piled up
because the same tool tries to cover both installation and
authoring use cases.
I've often had that thought, though I would say that M::B definitely
suffers from being a
# from David Golden
# on Monday 29 August 2011 08:07:
Eric raises the question why bother and I think for module authors,
at least right now, there is no burning platform to switch.
I think you misunderstand my point. Given dynamic_config support, there
is no need for a $builder_or_maker.PL
# from sawyer x
# on Sunday 28 August 2011 12:03:
a discussion of the effectiveness and CPU costs of SSL encryption
I didn't think it was a question of CPU speed anytime in the past
decade. How does a proxy cache encrypted data?
Atwood's Law of Computer Latency:
Processor cycles, storage
# from Gabor Szabo
# on Tuesday 09 August 2011 00:11:
So I tried
configure_requires 'File::Copy::Recursive' = 0;
require File::Copy::Recursive;
but that still blows up when I run Makefile.PL
That is to be expected. Something outside of Makefile.PL (i.e. the cpan
client) needs to have
# from sawyer x
# on Friday 29 July 2011 06:39:
I also personally see a case for security by default.
OK, please set your client accordingly. It's bad design to force this
at the server for all traffic.
Of course, it looks like the reasoning is encourage users to be logged
in at all times --
# from David Golden
# on Saturday 02 July 2011 03:51:
On Fri, Jul 1, 2011 at 9:23 AM, David Cantrell wrote:
... the complete lack of a reasonable set of
tools* on Windows, which just makes me angry whenever I have to
touch the blasted thing, made me stop.
* starting with a useable shell and
# from David Nicol
# on Tuesday 07 December 2010 14:12:
on_connect = $cb-($handle, $host, $port, $retry-())
This is confusing. If you're going to illustrate how it is called, take
it out of the context of how it is declared.
on_connect = sub {
my ($handle, $host, $port, $retry) = @;
# from Ovid
# on Thursday 09 September 2010 23:15:
sub foo {
my $self = shift;
my ($name) = @_;
...
I know this formatting is common, but what practical benefit does it
gain? ... I'm
unsure what value this provides other than conforming to a
particular coding preference (and it's
# from David Cantrell
# on Thursday 09 September 2010 23:32:
`$binary --version` =~ /(gnu|free software foundation)/i
I'm thinking something like ExtUtils::CheckForGNUbinary.
Scrap that. It should be more along the lines of checking for
capabilities rather than merely for GNU-ness, with
# from David Golden
# on Thursday 05 August 2010 08:55:
Though maybe I should just implement a feature to add '-TRIAL', since
I'll need that anyway for CPAN Meta 2 support. (Dist::Zilla already
supports -TRIAL).
Does search.cpan.org understand -TRIAL now? Last I looked, it was
properly
# from Guillaume Cottenceau
# on Wednesday 04 August 2010 13:12:
but I don't see
the big problem for machines and I don't know how to say hey this is
beta only with numbers; especially if 5.005_03 is equivalent to
5.5.30, I don't see how this could be considered to mark it beta/dev
The first
# from Gabor Szabo
# on Thursday 29 July 2010 05:11:
On Thu, Jul 29, 2010 at 9:16 AM, Johan Vromans wrote:
Much to my dislike I think we need yet another perl mailing list. I
didn't find anything suitable in the database of over 210 Perl
related mailing lists. Two lists come close:
# from James E Keenan
# on Monday 12 July 2010 16:08:
Agreed. In research I did on CPAN modules that contain XS,
ExtUtils::MakeMaker was still used 10 times as often as Module::Build.
It seems like authors lean toward EU::MM for XS because they've got so
many examples like that. Also, M::B's
# from Dave Cardwell
# on Saturday 03 July 2010 05:09:
I’ve written a module that wraps the notifo.com API ...
I’m leaning towards WebService::Notifo, but would appreciate your
advice if you would suggest otherwise.
WWW::Notifo::API or (Assuming that it's a REST API) maybe
REST::Notifo::API?
# from David Cantrell
# on Monday 05 July 2010 06:31:
consider Module::Build, but be aware that for a great many
users it will introduce an extra dependency, as it was not in core
until 5.10.0.
First, the great many is shrinking quickly, at least if Debian's
oldstable is any indicator of what
# from David Golden
# on Tuesday 29 June 2010 13:17:
... and each appender can be individually toggled on or off ...
... whether I want the issue detected at compile time or run time I
suppose, but is generally frowned upon to put imports down inside
class methods?
I tend to think about it
# from Paul Bennett
# on Sunday 13 June 2010 14:36:
As you'll be able to tell (with some digging), the tests that are
failing are one or more of the tests named
code/01-try-.*//code. These tests are all sanity-checks put in
place to test the underlying modules and/or libraries that my module
# from Hans Dieter Pearcey
# on Wednesday 12 May 2010 08:49:
...just because it's not how arrays work anywhere else in Perl,
This is not about how arrays work, but how functions work. See
localtime(), caller(), each(), glob(), readline(), etc.
But then see sort() and split().
There are
# from David Precious
# on Thursday 15 April 2010 11:32:
On Thursday 15 April 2010 17:04:44 Ovid wrote:
Never, never run the risk of breaking someone else's production code
if you can foresee this happening :)
100% agreed, that's why I think removing Perl6::Say from CPAN is a Bad
Idea.
Never
# from David Golden
# on Friday 02 April 2010 06:01:
On Mar 31, 2:51 am, tim.bu...@pobox.com (Tim Bunce) wrote:
It would be handy if there was a way for authors to indicate that
new maintainers are sought. Perhaps via the META.yaml/(.json) file.
...
It's not in the CPAN META spec ...
To me,
# from Andreas J. Koenig
# on Saturday 27 March 2010 21:02:
If you want to study the CPAN checkpointed logs solution running on
the very CPAN for exactly one year now: File::Rsync::Mirror::Recent
What needs to be done is really extremely trivial: rewrite it in C and
convince the rsync people to
# from cr...@animalhead.com
# on Thursday 25 March 2010 16:39:
CPAN on the smokebox was 1.9402, which can presumably act on the
CONFIG_REQUIRES in META.yml. Otherwise there would seem to be a
semantic knot wherein the 6.42 EU:MM doesn't know how to process
the new CONFIG_REQUIRES so it can
# from Jeffrey
# on Saturday 20 March 2010 20:32:
reference: https://rt.cpan.org/Ticket/Display.html?id=55909
I went back and
added the Marpa module to *both* the 'require' and 'build_requires'
for Marpa::HTML. Now all seems to work perfectly.
But it appears that you changed the rest of the
# from Jeffrey
# on Saturday 20 March 2010 20:32:
An obstacle for me was that Module::Build's actual behavior seems to
contradict the documentation in Module::Build::API, which says of
'build_requires' that
Modules listed in this section are necessary to build and install the
given module, but
# from Tamir Lousky
# on Friday 05 March 2010 01:16:
I liked the idea of putting in under the Algorithm::Shape namespace,
as it clarifies much better what it's for.
There is also Math::Geometry::, though Algorithm might be a good fit if
it is particularly algorithmic.
Shrubbery on the other
# from Skriptke
# on Wednesday 24 February 2010 00:54:
I have not managed to find documentation on whether it is possible to
include in MANIFEST files with spaces in names.
From ExtUtils::Manifest
Anything between white space and an end of line within a MANIFEST
file is considered to be a
# from Rene Schickbauer
# on Wednesday 24 February 2010 01:44:
Files with spaces are generally a BAD idea.
They can be inconvenient, especially in shell hackery.
For example, every time you call an external program, you have quote
the arguments. ... You can call `rm -f $fname`; right?
Which
# from cr...@animalhead.com
# on Friday 19 February 2010 09:15:
The [search.cpan.org] code is written in perl, right?
Nobody knows. Nobody has ever seen it. It doesn't exist.
Did you try using gitpan?
--Eric
--
You can't whack a chisel without a big wooden mallet.
# from cr...@animalhead.com
# on Thursday 18 February 2010 10:53:
I like to use this tool to confirm what I've changed from one
distribution to the next.
My latest one added two big data files, and 'diff' says its results
are too big to show.
Also the data files will change in future
# from cr...@animalhead.com
# on Sunday 07 February 2010 23:25:
I can
add the optimization I want to the extra_compiler_flags parameter,
but the optimization from the Perl build is included in the cc
command also. I feel sorry for the compiler which is told to
optimize two different ways...
# from Aditya Ivaturi
# on Thursday 04 February 2010 01:39:
WWW::... since it is actually going to use HTTP.
It doesn't talk to a single public service hosted on the World Wide Web,
so WWW is counter-descriptive.
This way, we don't end up with a new root namespace.
New root namespaces are
# from Shawn H Corey
# on Sunday 10 January 2010 08:11:
$ sudo cpan
This exposes your system to any bugs in the test suite (an accidental
`rm -rf /` has happened before) with root privileges. With a modern
CPAN client, you can set it to use sudo only at install time with the
# from Austin Schutz
# on Tuesday 12 January 2010 10:08:
Seems like it would be nice if the build system understood appropriate
behavior for the root user and acted accordingly. That is: given
superuser access privileges should be lowered by default during the
build process, but elevated for
# from David Cantrell
# on Saturday 09 January 2010 07:44:
Fine, but if you *don't* claim to have succeeded, then you have to
expect that software that looks for failures will spot the failure and
report it.
As the author's fault? Right.
--Eric
--
perl -e 'srand; print join( ,sort({rand()
# from David Cantrell
# on Wednesday 06 January 2010 03:48:
Exiting with a 0 status would seem to be the least clunky solution.
exit(0) means Stop now and claim to have succeeded
But you didn't succeed because something's wrong and thus on the way out
you must mention to the poor user what that
# from David Cantrell
# on Wednesday 16 December 2009:
Makes me wonder why fatal m/^Unsupported configuration: .*/
errors couldn't be made NA.
Mmmm, more special cases. From a user's (ie, a module author's) point
of view, isn't it easier to remember exit(0) than to remember
exactly what
# from Elliot Shank
# on Sunday 13 December 2009 12:58:
You don't fail the {Makefile|Build}.PL, you just don't emit the
resulting file and exit with 0. This way the standard build chain
treats it as a NA and not a FAIL.
This only has to do with cpantesters and *not* the standard build
chain.
# from Burak Gürsoy
# on Monday 14 December 2009 12:20:
Well... Either die OS unsupported\n is an exception (since I get NA
for that)
Yeah. Makes me wonder why fatal m/^Unsupported configuration: .*/
errors couldn't be made NA.
--Eric
--
Issues of control, repair, improvement, cost, or just
# from Andrew Espenscheid
# on Tuesday 01 December 2009 06:39:
I propose the following names for the modules
HTML::EditableTable
HTML::EditableTable::Horizontal
HTML::EditableTable::Vertical
Hi Andrew,
The 'tableTable' part of the name is a bit of a mouthful. What
about TableEditor? But,
# from Jonathan Rockway
# on Thursday 19 November 2009 07:06:
The real reason for the lack of another Perl VM is that Perl
programmers are very, very lazy. ;)
In this case, you mean 'perl' programmers. :-D
I seem to recall that we have a pressing need for another perl5 VM to
deliver on the
# from Ryan Voots
# on Monday 09 November 2009 06:17:
Why not just Github::?
I Thought the typical convention was to try to find some other root
namespace to put things in rather than making yet another one?
No, but that's a common misunderstanding. The recommendation is
roughly: Claiming
# from Paul LeoNerd Evans
# on Monday 19 October 2009 02:45:
Before I think about this though; does anyone have any better
suggestions? Are there other modules around with timing-sensitive
tests? How do they cope with variable load on the test boxes?
You might be able to do something with
# from Hans Dieter Pearcey
# on Saturday 17 October 2009 04:46:
There are a number of problems with this, but the biggest is that
nothing really does anything with 'recommends' in META.yml
Module::Build's 'installdeps' action will prompt you to install them.
Yeah, it's not CPAN.pm, but also
# from Jonathan Leto
# on Monday 21 September 2009 12:15:
It looks like the toolchain does not like the fact that I am using
MooseX::Declare in my Net::Topsy module [0]. It also had a hard time
figuring out my version number, until I hard-coded it in Build.PL .
That's Module::Build::ModuleInfo.
# from Jonathan Swartz
# on Friday 11 September 2009 18:08:
1) Don't bother putting $VERSION anywhere except the main module
This might get you '-1 set by base.pm' or other fun surprises from
Server::Control::Apache-VERSION.
2) Put a different $VERSION in each module, depending on when that
# from David Golden
# on Thursday 27 August 2009 19:12:
Except then it also needs to tell you that there's a new
Module::Starter and Dist::Zilla and App::Builder and Tool::Belt and
...
I'd limit it to toolchain modules that are dual-life CPAN and Perl
core. So M::B, EU::MM, EU::Install, etc.
# from David Cantrell
# on Friday 28 August 2009 04:10:
I guess maybe. It still seems arbitrary, and my point was that it
is a workaround to the fact that it's currently difficult for a
module to do the right thing to even compare its version against
the index.
I'd restrict it to only those
# from David Cantrell
# on Thursday 27 August 2009 07:33:
WARNING: there are new versions of Module::Build and Module::Install
available, it is strongly recommended that you upgrade them
CPAN.pm already tells you if a new CPAN.pm is available, ...
Except then it also needs to tell you that
# from David Golden
# on Tuesday 25 August 2009 17:46:
Install Archive::Tar. Upgrade Module::Build. That should fix it for
you.
This makes me wonder how many authors are using a current version of
Module::Build. Between this, configure_requires, and the
Software::License support, there are
# from Shawn H. Corey
# on Sunday 02 August 2009 07:56:
On https://pause.perl.org/pause/authenquery?ACTION=pause_04about it
states:
There's only one thing you need to know as soon as possible:
Please, make sure the filename you choose contains a version
number.
OK, does that mean every
# from Jonathan Yu
# on Tuesday 28 July 2009 09:37:
In at least one report, the version seems to be recent, so I'm not
sure if it's a new issue: version 0 0.76_06
It appears that you're using the deprecated (or soon-to-be-deprecated
(or maybe not deprecated depending on how
# from David Golden
# on Tuesday 28 July 2009 14:54:
Aside: I just do:
our $VERSION = v1.2.3;
But you shouldn't. :-) Unless you require Perl 5.10.
For some definitions of shouldn't perhaps depending on how much value
you place on which ends of the trade-offs. For everyday usage it's
# from Ovid
# on Friday 03 July 2009 06:40:
I can't find a proper parser for it and it turns out to have some
tricky bits. Basically, I want to do this:
my $duration = DateTime::Duration::W3C-new(P1Y2MT2H);
Are the tricky bits in the parsing or the calendar math necessary to get
to the
# from Geoffrey Leach
# on Monday 29 June 2009 12:34:
The key difference between Auto and Euclid is that Simon wanted to
subject the POD writer to minimal inconvienence. I should have
mentioned that option processing results in a call to main::foo, which
would permit the user to do whatever
# from Bill Ward
# on Tuesday 16 June 2009 15:08:
I know we're doing all kinds of crazy stuff to __DIE__ and I'm not
sure about __WARN__ but I suspect we may be.
You might like to try this as a way to assert that thou shalt not.
http://search.cpan.org/dist/Devel-NoGlobalSig
This assumes that
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
# from Eric Wilhelm
# on Sunday 24 May 2009:
I
want something which aliases an entire class hierarchy and loads
modules from it on demand.
use aliased::factory YAPI = 'Yahoo::Marketing';
# this does: require Yahoo::Marketing::KeywordResearchService
# and calls Yahoo::Marketing
# 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
Hi all,
I'm looking for something like aliased.pm, but with a more specific
functionality. Where aliased.pm only renames (and loads) one class, I
want something which aliases an entire class hierarchy and loads
modules from it on demand.
use aliased::factory YAPI = 'Yahoo::Marketing';
#
# from Thomas Klausner
# on Sunday 19 April 2009 12:28:
So. It seems there's nothing off the shelf that fits my needs. I
wouldn't mind contributing to one of the above projects (or to another
one..). But to which?
I've been using this for over a year now, but don't have time to
document it. It
# from Joshua ben Jore
# on Sunday 12 April 2009 20:06:
http://www.perlfoundation.org/perl5/index.cgi?perl_best_admin_practices
It may be a best practice to maintain your own perl but having just
done this at work, it's a massive time sink. Our new platform at work
is an Ubuntu mod_perl system
# from David Fleck
# on Sunday 12 April 2009 05:18:
On Thu, 9 Apr 2009, Eric Wilhelm wrote:
If you're installing today's code from the CPAN directly on outdated
production machines, you're doing it wrong.
So, what *should* you install on outdated production machines? Because
where
# from Dave Rolsky
# on Wednesday 08 April 2009 17:58:
I, as a module author providing you a free product, don't have to give
a damn. Realistically, authors give some amount of damn, but maybe
not a full I'll support Perl 5.004 for the poor slobs using ancient
Red Hat boxes.
Exactly. If you
# from David Cantrell
# on Thursday 09 April 2009 05:10:
But, anyway, is it a problem we really need to be inflicting on new
Perl users? Do they have to care if somebody might be running
5.8.8 somewhere? With 5.10.0 out for well over a year now?
I care because ...
You don't exactly qualify
# from David Cantrell
# on Thursday 09 April 2009 10:01:
The recommendations we make to new programmers are met with limited
patience. Do you recommend that they use EU::MM on account of
M::B not working on a system which hasn't been upgraded in 10
years?
No. But what about a system
# from Jonathan Rockway
# on Thursday 09 April 2009 13:30:
* On Thu, Apr 09 2009, Bill Ward wrote:
How about you write a how to manage Perl on your system doc and
get it into the core as a new perlxyz perldoc file then.
That is a very good idea.
Of course, the people that will update to a
# from Curtis Jewell
# on Thursday 09 April 2009 14:43:
On Thu, 09 Apr 2009 14:20 -0700, Eric Wilhelm wrote:
If everyone can get past the idea that something non-core is somehow
unusable, a fine document already exists
http://www.perlfoundation.org/perl5/index.cgi?perl_best_admin_practices
Ok
# from Hans Dieter Pearcey
# on Wednesday 08 April 2009 09:20:
In particular, saying maybe for Module::Build seems pretty
reasonable to me, since M::B vs. M::I is the emacs vs. vi of
distribution installers, and the summary there is controversy, but
it's definitely better than EUMM is
# from David Golden
# on Wednesday 08 April 2009 12:21:
On Wed, Apr 8, 2009 at 2:34 PM, Eric Wilhelm enoba...@gmail.com
wrote:
If there has been any controversy, it's been about the fact that
M::B was the first tool to break from how we used to do it. This
exposed
I'll add just my 2 cents
# from Hans Dieter Pearcey
# on Wednesday 08 April 2009 12:35:
On Wed, Apr 08, 2009 at 12:26:17PM -0700, Eric Wilhelm wrote:
You're saying there is a debate about whether stagnation is a good
idea?
I'm missing the connection between stagnation and Module::Install,
here. Or were you talking
# from David Cantrell
# on Wednesday 08 April 2009 16:17:
Dissenters are certainly free to hold their opinions without reason,
but I would rather they not inflict those irrationalities on others
as advice.
What you would rather has no bearing on what *is*.
And your belief that those who
# from David Cantrell
# on Thursday 02 April 2009 09:18:
Can anyone point me at a distribution which uses no_index/package or
no_index/namespace? I need a test case for CPAN::ParseDistribution.
I thought Alien-SVN, but that uses no_index/directory. Perhaps examine
the mldistwatch code or ask
# from David Golden
# on Thursday 19 March 2009 11:32:
I will look into this, but the problem with CC licenses is that
they are not Perl-approved - that is, they do not have fields in
Module::Build's license field
You mean not Module::Build-approved. Module::Build is obviously
buggy in
# from Ovid
# on Monday 09 March 2009 02:16:
Regrettably, no matter how much I play with the syntax, I can't get
something that's really convenient short of attributes and those
aren't terribly popular (and they're problematic since they aren't
Perl code).
The main trouble with attributes in
# from Ovid
# on Sunday 08 March 2009 09:48:
I want to write a module which allows me to quickly detect if a method
is overriding a parent class method
...
sub foo :override{...} # fails if it doesn't override
sub bar {...} # fails if it does override
...
use
# from David Golden
# on Tuesday 03 March 2009 12:02:
I would expect application of the Science to be found in the
Software Engineering program, but we've got a ways to go yet before
it becomes a professional discipline -- complete with licensing and
responsibility.
You might be interested
# from Joshua ben Jore
# on Monday 02 March 2009 08:20:
If you redesigned, replacing your hash with an array would be harder
to typo, faster, smaller, not as nice to dump with Dumper, and harder
for 3rd parties to extend.
Is harder to extend a design goal? You also make it harder to use.
And
Hi all,
This release is fairly minor in terms of changes from 0.31012, but with
this plus some recent improvements to CPANPLUS and TAP::Harness,
the just works feature seems to be working everywhere.
Module::Build now depends on TAP::Harness 3.16.
Thanks to David Golden, Jos, BinGOs, and
# from Jonathan Rockway
# on Thursday 19 February 2009 11:20:
* On Thu, Feb 19 2009, Ovid wrote:
The module in question should provide a sub or method to provide
access to this data.
This is a good point.
Java programmers learned long ago not to let people touch their
privates, Perl
# from Gabor Szabo
# on Saturday 14 February 2009 09:43:
Unfortunately neither search.cpan.org nor Kobesearch show them
correctly.
Yes, see 'encoding' in http://perldoc.perl.org/perlpod.html
http://search.cpan.org/perldoc?lambda
--Eric
--
Like a lot of people, I was mathematically abused
# from Bill Ward
# on Friday 13 February 2009 11:08:
What's wrong with Text::Abbrev? It's been part of the core for a
long time.
That might be the thing I'm looking for, thanks.
It does appear to have an issue with not detecting ambiguous
abbreviations.
my %hash = abbrev(qw(dog door));
# from Bill Ward
# on Friday 13 February 2009 12:22:
it can't find Module::Build!
I suppose I could use perl -I or PERL5LIB to specify the path, but I
was looking for something analagous to the LIB= argument that I could
give to Build.PL, and have that be propagated into the Build script
that
# from David Golden
# on Friday 13 February 2009 20:29:
I really wish there were some sort of standard process drafted that
would allow CPAN module developers to take over maintainership of
another (abandoned) module. Perhaps there is, and I'm just not aware
of it yet?
There is -- it's just
# from David Golden
# on Tuesday 27 January 2009 14:50:
On the other hand, maybe rt.cpan.org could become META.yml-aware and
redirect accordingly.
That's a lovely idea. Ambitious implementors may want to read:
http://use.perl.org/~Eric+Wilhelm/journal/38304
--Eric
--
perl -e 'srand; print
# from Jonathan Yu
# on Thursday 08 January 2009 12:03:
I just think you can have better
reusability while not compromising your ease of use, by setting
reasonable defaults and allowing those defaults to be overridden for
the special cases.
The interface is only via import(), so it's quite a bit
Hi all,
Thanks for the input and suggestions on this. I ended up with this sort
of usage:
perl -MDevel::NoGlobalSig=die ...
And that's on its way to the CPAN now.
# from Jenda Krynicky
# on Thursday 04 September 2008 10:22:
Why not make it slightly more general?
package CarpIfForgotten;
# from Slaven Rezic
# on Monday 15 December 2008 13:03:
I also had a smoke run on a FreeBSD machine running perl 5.8.8. I
found no surprises --- test failures and successes were more-or-less
consistent with MB 0.30 and 0.30_01, and the installed files looked
fine.
Thanks. I assume you noticed
Hi all,
An alpha tarball with the last few months' worth of fixes and
improvements is making its way toward your favorite cpan mirror as I
type this.
Authors will notice that they now need to install Software::License
before doing `./Build dist` and there will be a new file name LICENSE
1 - 100 of 334 matches
Mail list logo
