user-pic

Toby Inkster

  • Posted Book Report - September 2014 to Toby Inkster

    As you may be aware, I'm writing a book which will eventually become a free e-book. (Oh how I'm beginning to hate the e- prefix on everything vaguely related to computers. Or should I call them…

  • Commented on CPAN Testers & pre-requisite reporting
    The problem with these proposed solutions is that they assume that the release at fault is always going to be a trial one. I could release a seriously broken version of Exporter::Tiny as a stable release, and break a couple...
  • Commented on Event::Lib
    I'd suggest releasing 1.04 to CPAN straight away. As you're not the maintainer, it won't be officially indexed, so people won't be able to install it using: cpan Event::Lib Instead they'll need to install it like: cpan CRUX/Event-Lib-1.04.tar.gz Then, if...
  • Commented on Test::More has lots of crazy new development that's breaking my modules
    Exodist is making a lot of changes to the Test::More guts, which will hopefully lead to a much better Test::More. The aim is that the result should eventually be API-compatible with older Test::More. Because of the major changes, he's rightly...
  • Commented on Logically And Yourself (&&=)
    This is because the eval block isn't getting executed after the 4th iteration in your &&= case. You're effectively almost short-circuiting the loop. You could achieve a similar effect by inserting next unless $is_proofed; before the eval block in your...
  • Posted Object::Util to Toby Inkster

    I've recently released a new module called Object::Util to CPAN. This is a set of handy methods for working with classes and objects in Perl. It is inspired by

  • Commented on Install XML::LibXML without root
    The gist of how to patch XML::LibXML's Makefile.PL can be found in this ticket....
  • Commented on Install XML::LibXML without root
    A while back I created Alien::LibXML that installs a copy of libxml2 into one of your @INC paths. If you can install Perl modules, you can install it. Submitting a patch to XML::LibXML's Makefile.PL to check for Alien::LibXML has been...
  • Commented on Some new MetaCPAN features
    I really like the new version of the dashboard. Some suggestions: The bug counts could be a link to the issue tracker. Rather than using an "X" is those three centre columns, maybe use "R", "L", and "A". This is...
  • Commented on How does <email>@cpan.org work?
    The potential problem with them forwarding all mail unflitered to your primary e-mail address so that you can filter it, is that if you're filtering it yourself, you've lost out on one of the best ways to filter spam: originating...
  • Commented on Single-page POD for a distribution
    All versions of Opera prior to version 15 can do split screen....
  • Commented on Link to public version control system (GitHub or otherwise)
    A big improvement!...
  • Commented on Data::Dumper Debugging
    Yowch! Anyway, the first thing I do on any new Unixy box is: chsh -s `which tcsh` `whoami`...
  • Commented on I hate unpacking sub calls with shift
    Generally speaking I use shift for the invocant of method calls, or arguments I consider to be especially privileged. (If those arguments happened to be at the end of @_, I'd use pop, but that's not often the case.) Other...
  • Commented on Urging users with good test suites to test-drive latest DBIx::Class trial
    You have no access because people have been worried about what might happen if you find a way to harness the power of The Dark(pan) Side....
  • Commented on Quacks who write software make us all look bad
    It is possible that Dr Mato Nagel is a polymath and has doctorates in both medicine and sociology, though in this case I think your explanation is more likely....
  • Commented on Data::Dumper Debugging
    I don't know why bash users still reach for 2>&1 to pipe STDERR. Since version 4 (released five years ago), bash has supported a much simpler syntax borrowed from C shell and Korn shell: command1 |& command2 This combines STDOUT...
  • Commented on Data::Dumper Debugging
    Data::Dump doesn't have an equivalent of local $Data::Dumper::Deparse = 1;. And the $VAR1 = crud in Data::Dumper can be suppressed using local $Data::Dumper::Terse = 1;. Overall, Data::Dump does a better job with whitespace though....
  • Commented on Data::Dumper Debugging
    Perl warnings go to STDERR anyway, so I'm already in the habit of: perl whatever.pl |& less...
  • Posted Planet Moose - August 2014 to Toby Inkster

    Welcome to Planet Moose, a brief write up on what's been happening in the world of Moose in the past month, for the…

  • Commented on Data::Dumper Debugging
    Yes, I like Carp::Reply. It only kicks in when you reach an exception though. I like the idea of dropping into a REPL, poking around, exiting the REPL and resuming execution from there. Useful if you want to, say, poke...
  • Commented on Single-page POD for a distribution
    With multiple pages, you can open them in different browser tabs, or different terminals, and flick back and forth between them pretty easily. I'd actually expect the documentation to be harder to read if you were having to scroll up...
  • Commented on Data::Dumper Debugging
    Data::Printer produces nice output, and I used to use it quite a lot. I got frustrated by a couple of things though. For objects it shows a list of methods they have - awesome, right? However, it fails to show...
  • Commented on Rewriting Pod::Readme
    I've always taken the readme-from-pod route (which many people seem to do), but have recently been thinking that duplicating the information from the pod as a README file is fairly pointless. Instead a smaller README file containing the distribution's abstract,...
  • Posted Data::Dumper Debugging to Toby Inkster

    I've never really used the Perl debugger much (maybe I should learn?) and usually resort to lots of use Data::Dumper; print Dumper($somevar); statements to help me understand what's going wrong with a piece of code.

  • Commented on Link to public version control system (GitHub or otherwise)
    META.json allows two main fields for the repository - a URI for a web link, and also a VCS-specific string which often looks something like a URI. (There's a third field for the repo type - "git", "svn", "hg", etc.)...
  • Commented on Link to public version control system (GitHub or otherwise)
    The reason for the dramatic improvement you see may be a "CPAN Day" blip. Looking at the last 2000 uploads (as of now), 16% of them were uploaded by just one person - a person who happens to be quite...
  • Commented on Link to public version control system (GitHub or otherwise)
    The MetaCPAN dashboard thingy is buggy though. Mine shows dozens of distributions that it claims have no link to version control. An example is LV. This quite clearly includes a version control link in META.json and META.yml, which is clearly...
  • Commented on Introducing IOD file format
    It doesn't seem quite the same. In a traditional INI file: [section] foo=1 bar=2 bar=3 "bar" is an array, but is "foo" a simple string, or is it an array with just one element? The INI parser will probably treat...
  • Commented on Type::Tiny 1.000000 Released
    Ivan, have you read Type::Tiny::Manual::Libraries? That's probably the best starting point for creating a type library....
Subscribe to feed Recent Actions from Toby Inkster

  • exodist7 commented on Test::More has lots of crazy new development that's breaking my modules

    As the person making the Test::More changes, I have to agree with this idea:

    Failures due to alpha versions of Test::More should not be red marks against OTHER modules that in no way took action to cause the problem.

    If I had known they did show up there I probably would have been reluctant to release these alphas. The alphas are valuable and help me find a lot of issues... but I don't want other people to be dinged from them. I myself judge modules based on the pass/fail ratio in cpan testers.

    At the very least these should be unknown, not fail (in metacpan/cpan dis…

  • Ether commented on CPAN Testers & pre-requisite reporting

    > The "DEVREL" prefix will be appended as soon as there is *anything* in the chain

    I like this a lot, and it's similar to what I was thinking too. However, I realize now there's a problem here -- the release status of a module can't always be determined from the module itself (at least, not the $VERSION) - you need the distribution metadata to determine that.

    There is one (relatively) simple way to handle misdirected failures, however -- allow a mechanism to redirect them. We've already got nearly that, with the new admin site -- just modify the interface to allow redirectin…

  • exodist7 commented on CPAN Testers & pre-requisite reporting

    I agree with Peter Rabbitsons solution, I left a comment to that same effect in the original post.

    I am the one making these Test::More changes, and I would have been a lot more reluctant to make these alpha releases if I know it would give other people red marks. I myself judge modules based on red vs green counts.

  • CPAN Testers commented on CPAN Testers & pre-requisite reporting

    Your assumption that there would be virtually no changes after the Metabase is incorrect. There would be several. Again we've had this discussion before and as Toby also points out, the problem dependency may be nothing to do with the distribution that is a development release. It is not a trivial task to check this in the client either.

    My intention, as Ether notes, is to use the Admin site to allow others to correctly attribute the report to the offending module. It's a slightlymore long-winded and manual process, but it will be more consistent when re-attributing reports.

  • Peter Rabbitson commented on CPAN Testers & pre-requisite reporting

    I still maintain that "oh, changing the set of test tags beyond the current 4 is too hard" is a dead-end strategy. In order to remain relevant the cpantesters infrastructure must allow for extra test-type additions anyway - the current set is too limited.

    In addition I do not believe (given I know and admire the skill of everyone involved) that the current stack is written so badly, that it will be a monumental effort to allow for "super-namespacing" of the test results. At worst it should be a couple day slog, perfect for a hackathon... if there only was an upcoming one ;)

    T…

Subscribe to feed Responses to Comments from Toby Inkster

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.