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.
    • When I attempt to run my perl programs it says "Only .pl files can be executed" Almost none of my perl programs are named something.pl. But they do all start with a #! line. Padre should have mulitple ways to check the type of file if it's going to do the check.
    • Textmate has a panel on the side (much like where you have the subroutine names now) which allows for filesystem navigation. Such a thing would be useful in Padre. Perhaps have that side panel be tabbed too, with one tab showing the subroutines in the currently selected file and the other tab showing the filesystem. (Or do like textmate and put the list of subs in a pop-up that appears along the bottom of the window)
    • Links to the documentation for perl functions. Clicking on "push" in one of my programs, for instance, should pull up a window the the push docs in it. Bonus points would be doing the same sort of thing but for any arbitrary module that happens to be used.
    • vim-mode :-) I still prefer to use the keyboard ala vi rather than the mouse.
    • integrated test support. I should be able to run tests and if any fail, link directly from the failure report to the failing test.
    • subroutines names should match /\w+(::\w+)*/ Right now it looks like it's only getting the first identifier.
    • Ah, it looks like I'm not the only one to have this idea. For a poor-man's version of vim+textmate marriage, see http://vimmate.rubyforge.org/ [rubyforge.org]

      It's no where near as full featured or as "clean" as I would want it though.

    • Responses:

      The .pl files limitation is imposed by the first (pre-document-model) generation of file type code. We should be able to upgrade this fairly easily by adding perl type awareness to the ::Document::Perl class and then upgrading the limitation.

      The tabbed list on the right is a want-to-have already, you can see it's currently got that extra space at the top where the tabs should hopefully appear. Additionally, a file tree needs to wait for Project support.

      Anything that allows linking to function docu