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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
more productive? (Score:1)
Reply to This
Re:more productive? (Score:2, Insightful)
Syntax highlighting on the other hand makes it very easy to spot typos in Perl. If you mis-quote something, or leave off something you shouln't, you'll know it because the next few 'paragraphs' of code will be the wrong color.
Code completion (Score:3, Insightful)
In Java, I find it useful for when I'm learning a new library. It's also decent for using libraries that
implementLongFunctionNamesForEverything()so I can just type 'imp<TAB>' and pick the right one. In that other language, it's also useful for argument order, particularly for overloaded methods.Chris
M-x auto-bs-mode
Re: Code Completion (Score:2, Informative)
Automatic code completion would probably annoy me too, but in Vim I find
Ctrl+Pinvaluable for completing partially typed words.For example if you have a variable called
$inner_template_filenamethen merely typing$innthen pressingCtrl+Pwill type this. It's a great time-saver, reduces typos, and means that using meaningful identifier names is much less painful.(There's actually slightly more to it:
Ctrl+Prepeatedly cycles through different previously-used words that caRe: Code Completion (Score:2, Informative)
-Dom
Re:more productive? (Score:1)
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 th