user-pic

Matt S Trout (mst)

  • Commented on Perl's Pegex Module: a great way to parse files by creating grammars
    Ron: If the article was insufficient for *me* to understand why you think PEG is "dangerous", I fail to see how it's going to help beginners at all. Jeffrey: Nah, I read it as a regex-like thing and got the...
  • Commented on Perl's Pegex Module: a great way to parse files by creating grammars
    I'm afraid that article doesn't seem like a convincing argument unless you accept the author's premises a priori. Certainly the second example (A = "a"A"a"/"aa") was entirely obvious to me, and yet was clearly chosen to try and demonstrate a...
  • Commented on Missing Smart Match
    Actually, there's already Syntax::Keyword::Junction which is a cleaned up fork that's explicitly extant to avoid the Perl6:: thing (and is maintained by the usual suspects). -- mst...
  • Commented on Missing Smart Match
    If somebody can figure out a way to do pluggable ~~ that isn't even more confusing than what we currently have, the future is filled with possibilities. So far, nobody has, so the status quo remains. -- mst...
  • Commented on Missing Smart Match
    The problem is "just fix the bugs" will break things that rely on the currently documented behaviour. Also, making it pluggable had allllll sorts of fun scoping issues, and nobody was able to find a sufficiently sane approach to dealing...
  • Commented on Virtual Spring Cleaning (part 9 of X) wherein I retrieve content
    Future:: is a namespace for future implementations and extensions, and your module is going to cause much confusion in its current namespace. I'd suggest maybe HTTP::UserAgent::FutureBased or similar? -- mst...
  • Commented on Overview of current maintainer fails
    There are a number of inaccuracies in this post, not just whether certain modules are maintained, but who the maintainer(s) is/are, and whether they have merged various fixes. This data is not to be trusted and should be considered more...
  • Commented on The removal of the lexical topic feature in 5.24
    The _ prototype failed to be adopted long before the experimental pragma arrived on the scene, much though I guess that doesn't fit the desired narrative. I find it fascinating that in spite of reini's assertions to me on Twitter...
  • Commented on Test2/Test::Builder Update from the QAH
    Oh, chansen, I see you're having a 'yelling at people based on incomplete information' day again (though this comment is still better than our IRC comment telling the new pumpking to 'get your shit together' on his first day when...
  • Commented on The removal of the lexical topic feature in 5.24
    The _ prototype doesn't really help with things like @$ so far as I can see, unless you're saying that I need to rewrite everything that's currently 'foo { ... } ...' to 'foo sub (_) { ... } ...'...
  • Commented on Test2/Test::Builder Update from the QAH
    > I recall there was moves to propose a 3rd way, the "don't integrate yet, but have a way to smooth over our transition more progressively before we finally commit". We've already spent an extra year moving progressively and smoking...
  • Commented on The removal of the lexical topic feature in 5.24
    While, yes, ok, 'any' can thereby use the lexical topic, what about pure perl implementations of similar things using &$ signatures? My problems with lexical $_ have never been exactly core-implementation-related so much as "I have so much code that...
  • Commented on Test2/Test::Builder Update from the QAH
    So far as I can see, in the absence of a viable third way, the options on the table were, basically, 1) Don't merge it 2) Merge it and see what happens, and if necessary unmerge it until we can...
  • Commented on Test2/Test::Builder Update from the QAH
    So, while I've definitely disagreed with Exodist at various stages of the process (FVO 'disagreed' that included at least one fairly lengthy yelling session which, in hindsight, might have been more likely to make him quit than to listen to...
  • Commented on Virtual Spring Cleaning (part 2 of X) in which I release Apache::Tika::Async
    Given Future already supports all of the different loops, as soon as you load an event loop at all it's effectively free. Search::Elasticsearch chose Promises for no particular reason and the author was open to adding Future support as well;...
  • Commented on Virtual Spring Cleaning (part 2 of X) in which I release Apache::Tika::Async
    Dude, please don't call it that! ::Async indicates IO::Async components, which when written using Future.pm interoperate well with the rest of CPAN, including POE, Mojo and provided you bypass the AnyEvent landmine, AnyEvent code too. AnyEvent already tries to break...
  • Commented on A Date with CPAN, Part 1: State of the Union
    Current short version: Use Time::Moment for performance, DateTime for the ecosystem, or Time::Piece for ease of fatpacking. If you want to make CPAN better, a pure perl implementation of Time::Moment or starting to port some of the DateTime ecosystem would...
  • Commented on Uploading a new package
    A perl dist of the form Foo-Bar-Baz-1.23.tar.gz needs to contain a package Foo::Bar::Baz or it will be rejected by PAUSE. This is normally done by adding a file lib/Foo/Bar/Baz.pm that declares the package in the normal way. In the case...
  • Commented on Statistics for perl hash tables
    "What is not good is that the developers have no idea how to evaluate hash tables and there is no sane discussion possible in the mailinglist" Asserting that nobody except you is competent to have an opinion does, indeed, largely...
  • Commented on Some ideas for improving the community - The ANA initiative
    You appear to misunderstand how open source works. "we need" is irrelevant. Actions speak louder than words. Patches speak louder than suggestions. Some of the things on this list are a good idea, some aren't. However none of them will...
  • Commented on Test::More - New Maintainer, Also stop version checking!
    This is awesome to hear. Organisations are an excellent tool and it's nice to see there being more and more of the Catalyst/DBIx::Class/Moose model of open discussion online and on IRC with multiple committers and shared ownership, and to give...
  • Commented on Crowdsourcing self-confidence
    Recruiting for a long standing project with a high barrier to entry and an architecture that's bulging at the seems is hard. During the periods when I've tried to be more active, I've not been able to give out nearly...
  • Posted Hallway++ at YAPC::NA 2013 to Matt S Trout (mst)

    Interested in meeting new people at YAPC::NA? Hallway++ means you're never interrupting

  • Posted An Incident Summary to Matt S Trout (mst)
  • Posted On Codifying Conduct to Matt S Trout (mst)
  • Commented on How do we know when a CORE module is deprecated?
    Petdance, anybody else who happened to be in #perl for the whole conversation will have seen: wasanzy asked for help Shells suggested something that's a really bad idea apeiron corrected this Shells, apeiron and I discussed it until Shells understood...
  • Commented on How do we know when a CORE module is deprecated?
    Steven, it can be preserved on CPAN for the people with legacy code that requires it. Given the existence of Plack::Handler::CGI, starting a new project with CGI.pm in 2013 out of anything except ignorance is simply gross incompetence....
  • Commented on How do we know when a CORE module is deprecated?
    I believe it's leaving core as of 5.22.0 'deprecated' is generally taken to mean "should be avoided because it's been superceded", which CGI.pm very definitely has as of the release of a Plack with CGI support....
  • Commented on How do we know when a CORE module is deprecated?
    Joel, you still don't have any of the context for this, or the help that's been given to wasanzy over the previous weeks and months. I do, however, apologise to anybody who read this blog post before the author fixed...
  • Commented on How do we know when a CORE module is deprecated?
    Coke, Chris Fedde and apeiron have had an axe to grind against each other for years. apeiron decided to put him on /ignore to avoid getting into any more non-constructive arguments. cfedde apparently has gone the "passive aggressive blog post...
Subscribe to feed Recent Actions from Matt S Trout (mst)

  • Flavio Poletti commented on Missing Smart Match

    Didn't know about Syntax::Keyword::Junction, that's what you get when you stop to the first module that fits the requirements :). It would be good to have some hint in the Perl6::Junctions docs, anyway, because it seems "more popular" with two reviews and a few more ++'s. Maybe even a new comment would do the trick?

    The new subs in List::Util are OK but they (understandably) follow the syntax of the rest, which is less sugary. This seemed to be an important point in the OP. How much sugar you like is a matter of taste, of course.

    I agree with Graham Knop and I consider any(…

  • Aaron Priven commented on Missing Smart Match

    $x in @m and $y ~> @n are analogous to and just as comprehensible as $x eq $m and $y == $n.

  • Ron Savage commented on Perl's Pegex Module: a great way to parse files by creating grammars

    Matt

    Sure, but you're judging it from the point of view of an expert. My aim is to warn beginners of the dangers.

  • Jeffrey Kegler commented on Perl's Pegex Module: a great way to parse files by creating grammars

    Thanks for looking at my piece. Most users will read the PEG A = "a"A"a"/"aa" as if it was BNF or a regex, in which case the number of "a"'s clearly must be a multiple of two. But to match in PEG, the count must be a power of two.

    This was not obvious to the author or referees of the article from which I took the example. It is shown by formulating and solving a recurrence. The mathematician John von Neumann was famed for his ability to formulate and solve these off the top of his head, but I wonder if you perhaps, at this point in my article, read me a bit has…

  • Jeffrey Kegler commented on Perl's Pegex Module: a great way to parse files by creating grammars

    Intuitions certainly can differ. I may add more about PEG to my "Parsing: A Timeline" piece: http://jeffreykegler.github.io/Ocean-of-Awareness-blog/individual/2014/09/chron.html PEG's algorithm in fact goes back to the pre-YACC compiler-compilers of the 1960's.

Subscribe to feed Responses to Comments from Matt S Trout (mst)

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 hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.