Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Considering this:

    my $arrayref_of_hashes = SELECT * FROM table_name;

    I think it gains me nothing. Nothing at all.

    Considering this:

    method morning (Str $name) {
        $self->say("Good morning ${name}!");
    }

    If I can get that (amongst other things), I will cheerfully give up:

    • No/degraded syntax highlighting.
    • No/degraded PPI parsing.
    • No/degraded shiny Padre refactoring tools.

    Different people value different things. I'd hate to give up the items on that list, but I'd much prefer to work with a program

    • That's why D::D should only be a prototyping tool and eventually such features should be available from the core.

      Note, however, that making the new syntax available with a "feature" invocation carries virtually the same problems as D::D. You never know from static analysis (and non-recursive) whether it's on or not. But at least this would mean it's blessed and to be considered part of the language.

      • Well, the difference with use feature is that at least in that case it's official, in the core, works the same on every operating system and every host, and doesn't require the parser to leave the document.

        So it's possible to add the relevant special casing in, where in the generic DD case that is not true.

        • Not really. Consider Modern::Perl, common::sense, and their ilk. And besides the ones on CPAN, any codebase can contain its own equivalent. Sure, you can special-case strict.