,
--
Aristotle Pagaltzis // http://plasmasturm.org/
modules within a distribution is a non-
obvious precondition for dependency resolution to work 100% reliably in
all edge cases. I have notes for an article about it flying around here
somewhere that I should really get around to writing and publishing.
Regards,
--
Aristotle Pagaltzis // http
/::([^:]*)$/print$1,(,$\/, )[defined
wantarray]/e;chop;$_}
Just-another-Perl-hack;
#Aristotle Pagaltzis // http://plasmasturm.org/
* Matt Simerson m...@tnpi.net [2013-05-11 06:30]:
I've noticed that quite a few modules have maintainers, who take over
when an author goes AWOL. What is the process for for achieving that?
http://www.cpan.org/misc/cpan-faq.html#How_adopt_module
emphasise futures rather than IO::Async, natch.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Paul LeoNerd Evans leon...@leonerd.org.uk [2013-05-27 01:35]:
On Sat, 25 May 2013 08:52:30 +0200
Aristotle Pagaltzis pagalt...@gmx.de wrote:
That’s just what futures are for, I think? As in, they abstract the
sync/async control flow out of the code. And you’re just putting that
on top
themselves.)
I don’t follow. Do you mean they should get a GD::Image that has methods
for both algorithms, or something along these lines?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
this Regexp::Builder.
--
Aristotle Pagaltzis // http://plasmasturm.org/
one. (Alien::NotVMS::FooBar?)
--
*AUTOLOAD=*_;sub _{s/..([^:]*)$/()[print$1,(,$\/, )[defined
wantarray]]/e;$_}
Just-another-Perl-hack;
#Aristotle Pagaltzis // http://plasmasturm.org/
://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/lancaster-consensus.md#flagging-abandoned-modules-and-modules-requesting-help
[1]: https://metacpan.org/author/ADOPTME
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Aristotle Pagaltzis pagalt...@gmx.de [2013-08-22 04:23]:
[1]: https://metacpan.org/author/ADOPTME
Hmm, http://search.cpan.org/~adoptme/ seems better for this case…
--
Aristotle Pagaltzis // http://plasmasturm.org/
-another-Perl-hack;
#Aristotle Pagaltzis // http://plasmasturm.org/
* Jean-Damien Durand jeandamiendur...@free.fr [2013-10-30 01:00]:
I liked
- JavaScript::Transpile for its explicit namespace and play on words
translate/compile (that's my interpretation, Aristotle)
Not my coinage. https://en.wikipedia.org/wiki/Transpiler
--
Aristotle Pagaltzis // http
be thought of yourself by someone else?
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
--
Aristotle Pagaltzis // http://plasmasturm.org/
* it to the
whole kit and caboodle, the name becomes ludicrous. So I left it out.
So that’s the best I could do.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
Then a few `git rm -f META.yml git rebase --continue` later you’d’ve
gotten what I think is just what’s in your pull request.
--
git commit -m 'Just another Git hacker,'
#Aristotle Pagaltzis // http://plasmasturm.org/
* David Cantrell da...@cantrell.org.uk [2013-12-12 20:40]:
On Sat, Dec 07, 2013 at 02:38:46AM +0100, Aristotle Pagaltzis wrote:
* Shlomi Fish shlo...@shlomifish.org [2013-12-04 15:30]:
Well, git rebase did not work properly (too many silly merge
commits for stuff that predates my
thing that can happen is that the user lacks the experience to
understand the state they put Git into, and how to change it (back, or
in any other direction) – but not actual data loss.
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Yanick Champoux yan...@babyl.dyndns.org [2013-12-22 20:35]:
Perhaps a saner middle-ground could be of introducing a new
environment variable CPAN_NO_MAJOR_JUMP.
Or just warn instead of dying.
--
Aristotle Pagaltzis // http://plasmasturm.org/
to tweak the environment to
taste. Not sure which one would be the less leaky abstraction.)
--
Aristotle Pagaltzis // http://plasmasturm.org/
to be brittle: if
you are shipping a tarball of the alien or downloading a particular of
it version during *.PL, you know exactly what’s in the tarball, so you
know exactly what your patch code will do.
--
Aristotle Pagaltzis // http://plasmasturm.org/
squatted on the
preferable term, so it’s still yours for the grabbing.
So, congratulations on your shiny new Net::Domain::PublicSuffix module.
:-)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
* Ben Deutsch b...@bendeutsch.de [2014-09-18 20:20]:
Text::Template::LocalVars
FWIW, that was going to be my suggestion too.
--
Aristotle Pagaltzis // http://plasmasturm.org/
release until you have settled the namespace question.
--
Aristotle Pagaltzis // http://plasmasturm.org/
in cursory search. Seems a decent enough name.
So, CPU::Mic1::Assembler? With “MAL” mentioned in the abstract so a CPAN
search will find it?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
value is
supposed to be just a string, you should surround it with \Q and \E.
FTFY.
It’s not just paths.
(You don’t need to quotemeta *every* time of course – but you *should*
reflexively stop and consider *whether* you need it, every time.)
Regards,
--
Aristotle Pagaltzis // http
sign up for that too. So whatever is all
fine with me, I don’t care.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
,
--
Aristotle Pagaltzis // http://plasmasturm.org/
it
become unlikely to be found by undirected search.)
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
; So, please, do not remove META.
Nobody is talking about dropping META entirely. The question is whether
a META.yml is necessary in addition to META.json.
Does dh-make-perl need META.yml specifically or can it just as well use
META.json? (I would hope it can…)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
, but figuring out when you need it and when not is a hassle,
> and actually declaring a minimum EUMM version (even if it's an ancient
> one) is generally considered good practice. Also I think some
> packagers may be using it.
So what does that mean for John’s original question?
--
A
out of the box.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
modules, and
that did turn up another alternative: those are split between Devel::
(again) and Sys::. Oh right, d’oh. That seems like a pretty good choice.
How does Sys::DTrace::Consumer sound?
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
.
You’re monkeypatching lib.pm. How about lib::RespectHooks?
That would be particularly descriptive if you avoid the need for any
interface by simplifying the code to something like
my $newimport = sub {
my @hook;
push @hook, shift @INC while ref $INC[0];
&$originallibimp
se. But
note that you cannot turn off pull requests at the time of this writing.
So in practice modules maintained under a personal account are not that
problematic. The only serious problem is in case the maintainer got run
over by a bus and nobody else can log into their GitHub account.
Regards,
--
fuss of it myself on behalf of
Neil without asking him, and to leave it to Neil whether he wanted the
point addressed.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ole document they always get bytes.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
s? Sounds like Algorithm::QuineMcCluskey would be separate
but the others would ship together. If so, then one should probably be
a sub-namespace of the other.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
want to use these packages. (Which doesn’t have to be a CPAN
module, it can also be some would-be user’s already-existing code base.)
It will be uglier to namespace your stuff more; bite that bullet.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
that line was supposed to be doing.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Aristotle Pagaltzis <pagalt...@gmx.de> [2017-01-09 01:42]:
> * Konstantin S. Uvarin <khe...@gmail.com> [2016-12-27 11:24]:
> > perl -Mnew=x=My::Very::Long::Module,foo,42 -we "print $x->foo;"
>
> perl -Maliased=My::Very::Long::Module,X -we 'print X->
101 - 142 of 142 matches
Mail list logo
