user-pic

Leon Timmermans

  • Commented on Managing Boilerplate with Import::Base
    This is a terrible idea really: any change to your bundle mean breaking backwards compatibility. This sort of breakage-at-a-distance can be hard to diagnose. To some extend you can deal with it using a versioning argument (like Modern::Perl does nowadays),...
  • Commented on Strawberry Perl 5.20.1.1 invalid MSI signatures
    Quite frankly anyone asking for a scanned copy of an identification document is an idiot: you can not verify the authenticity using a copy. Even a crappy forge is likely to be accepted. Sending it by non-encrypted email doesn't make...
  • Commented on A pre-release of Pod::Readme is available on CPAN
    Why the dependency on Moose and v5.10? The latter seems rather unnecessary, and the former poorly chosen (lots of dependencies, while using few of it's features: Moo sounds like it would be much more appropriate)....
  • Commented on How should conference speakers be compensated?
    I think there are two kind of sponsored people. The first category are the Damians of our community. These are people whose attendance at any conference provides an immediate and obvious benefit every time you'd invite them. People like me...
  • Commented on Introducing IOD file format
    Have you taken a look at [TOML](https://github.com/toml-lang/toml)? IMO it provides a much more sensible paradigm than INI, while still being intuitive enough for most people. There are already two parser for it in Perl....
  • Commented on A Tale of Two YAPC's
    Sounds like excellent choices have been made....
  • Commented on I hate Dist::Zilla and missing Makefile.PL
    More often than not you can hack on a module without Dist::Zilla just fine. Tests can usually be run simply as `prove -lr t/`, so usually you can actually hack on the code and test the results without touching dzil....
  • Commented on Introducing Sub::Trigger::Lock
    You're not locking the external access, but the internal implementation. IMO that's the wrong solution....
  • Commented on How to upload a perl module on CPAN using Dist::Zilla?
    Actually, you need to use a semicolon as comment character ;-)...
  • Commented on Perl and Me, Part 1: The Road So Far
    > It looks interesting; it seems to solve several of C++'s more egregious problems (e.g. garbage collection). Actually, I consider garbage collection to be the main mistake in D. In such a low level language, I don't want garbage collection....
  • Commented on Visualizing a CPAN install plan
    > I've always wondered why CPAN does not at least show a full dependency list (what will be pulled in, not necessarily the full dependency list) similar to the way that yum does prior to launching into what can turn...
  • Commented on Is it possible to run Movable Type under Apache HTTP Server?
    CGI still lives for the same reasons as inetd still lives: services that are queried only infrequently (with a "frequently" being defined by the sysadmin), keeping a process in memory is wasteful. Exactly. CGI is the only sensible thing...
  • Commented on A new blogs.perl.org or die trying
    Yeah, I'm not fond of it either. I can't help thinking "wouldn't a simpler solution be better here?"...
  • Commented on Parsing JSON with a single regex
    Awesome. XML parser next?...
  • Commented on PDL 2.007 Released!
    This PDL release was the driving force behind File::Map fixing some 64-bit related issues, so thank you Chris and Rob :-)...
  • Commented on CPAN candidates for adoption
    The scoring mechanism doesn't seem to have much of a resolution. Many of those dists don't need adoption at all. One module of mine is in there because it has two wishlist tickets…...
  • Commented on Plack server with threads
    > It is only one thing that breaks everything: threads::shared. That really shouldn't happen. Either you're not using it correctly, or something really weird is going on....
  • Commented on A decade in CPAN toolchain
    people expect to build, test and install in separate phases It's not just that people expect it, it's that sysadmin will demand it. Friendliness to the end-user is just as important as friendliness to the author, if not more...
  • Commented on Why you don't need File::Slurp…
    There's a flaw IMHO, read() may not return the whole file content (and actually it won't with large files), depends on OS buffering. The usual boilerplate includes a while() and buffer concatenation. Actually, you're right. Normally the buffering takes...
  • Commented on Response to Ejecting CGI.pm From the Perl Core
    > I use Perl v5.8.0 on windows (ActiveState). That is a 10+ years old release of perl. Are you really surprised its modules are way outdated?...
  • Commented on On the removal of some core modules
    Leon has started his own Module::Build::Tiny and while admirable (and impressive) it cannot do XS yet. Until this is possible or until Moodule::Build or some other candidate emerges, EUMM and MB are the only way to go. Actually, I...
  • Commented on Belated "hello world"
    Good to have you here, curious what you have to say :-)...
  • Commented on Why you don't need File::Slurp…
    Because File::Slurp is portable to non-Unix systems. Functionally it's identical to read_file(binmode => ':raw'), otherwise it's perfectly portable. Because File::Slurp can be rewritten in XS if speed is the overriding concern (and it will be faster than your 2-lines)....
  • Commented on Why you don't need File::Slurp…
    If I recall, File::Slurp had issues with the PerlIO :encoding layer and required manual decoding of the slurped data instead, which is why I have avoided it. Not sure if this is still an issue. Looking at the code,...
  • Commented on Why you don't need File::Slurp…
    mmap should be faster than sysread -s or read -s, and there exist a portable module for it. There is, and I wrote it ;-). Was planning to blog about that too at some point. It's close but not...
  • Commented on Why you don't need File::Slurp…
    In general, in a shop with both newbs and monks it's preferable to use modules as much as possible. You're missing the point; I'm all for modules, I didn't write 50 CPAN modules for nothing. This code started when...
  • Posted Why you don't need File::Slurp… to Leon Timmermans
    #! /usr/bin/env perl
    use strict;
    use warnings;
    use Benchmark 'cmpthese';
    use File::Slurp 'read_file';
    
    my $filename = shift or die "No argument given";
    my $count = shift || 10;
    
    cmpthese($count, {
        'Unix'  => sub { open my $fh, '<:unix', $filename or die "Coul…
  • Commented on I Bless You in the Name of the Stringified Object
    I'm wondering if a "::" overload makes sense, specially if a future version of perl would allow for blessing into an anonymous stash....
  • Commented on Introducing Platform
    Instead of having a hard-coded list of osnames you might want to rely on Perl::OSType. Though as Mr. Muskrat said there are some tricky bits such as cygwin....
  • Commented on Don't release experiments to CPAN
    I agree with David. I release experiments to CPAN. Sometimes I don't do anything with it anymore, but someone else might. Because letting code rot in a corner is a waste of effort. That said, most of my experiments are...
Subscribe to feed Recent Actions from Leon Timmermans

  • Mike Doherty commented on Why you don't need File::Slurp&#x2026;

    Would you benchmark this method of slurping, which is what I typically see?

    my $contents = do { local $/; open my $in, '<', $filename; <$in> };

    Might be worth adding to https://github.com/melo/perl-benchmarks

  • Damien "dams" Krotkine commented on Why you don't need File::Slurp&#x2026;

    I like to use this for non production code :)

    my $content = do{local(@ARGV,$/)=$filename;<>};

    I don't think it's useful to benchmark it :)

  • Ether commented on A pre-release of Pod::Readme is available on CPAN

    What limitations are there as a result of not using a full POD parser? Are there certain syntax elements that are not recognized, a depth limitation to nested elements, etc?

  • Robert Rothenberg commented on A pre-release of Pod::Readme is available on CPAN

    @leon I am in the process of changing it from Moose to Moo.

    As for v5.10, I prefer using some of the features of v5.10 to simplify the code. If I get enough feedback from module authors asking for support of 5.8, I'll look into changing that. (Note: this module is intended for module authors, and shouldn't be necessary just to build a module.)

    @ether: Bugs in previous versions were always due to limitations of different POD parsers, which is why I gave up on trying to use one. The current version only cares about =begin/=end and =for elements, really, though it doesn't suppor…

  • preaction commented on Managing Boilerplate with Import::Base

    Could you give an example? As far as I know, everything in the bundle is scoped lexically, so it only affects my project, not other projects using my project. Other projects are allowed to use the included base bundles, sure, and yes, if the bundle changes, it could potentially affect anyone who uses it.

    Ah. I think I forgot to mention how I manage bundles by giving every CPAN-style dist of at least medium size its own ::Base module, or if the main namespace has no other purpose, making that the base module: Statocles::Base, App::YAML::Filter::Base, Freyr::Base (not on CPAN yet).

Subscribe to feed Responses to Comments from Leon Timmermans

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.