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.
  • Does all of that stuff really make you more productve? I find that syntax highlighting and "code completion" just get in the way more times than not. Thus I use vi in all it's varied guises and I'm perfectly happy.
    • Does all of that stuff really make you more productve? I find that syntax highlighting and "code completion" just get in the way more times than not. Thus I use vi in all it's varied guises and I'm perfectly happy.

      I'd really hate to go without syntax highlighting for anything significant. It helps catch a lot of errors earlier. The implementation in vim [vim.org] catches a number of stupid typos before I try to run the code. I've tried various code completion things, but I've never found any that worked better than just typing. I had paren completion (it would put in the right of whatever left paren -- (, [, or < -- I put in. That was much more trouble than it was worth.

      Hint! This seems like it'd be a nice survey!