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.
    • by Mr_Perl (2788) on 2002.04.25 15:00 (#7538)
      Code completion annoys me. It seems intended to be a crutch for those who don't yet know the language very well.

      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.
      • 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

      • Code completion annoys me.

        Automatic code completion would probably annoy me too, but in Vim I find Ctrl+P invaluable for completing partially typed words.

        For example if you have a variable called $inner_template_filename then merely typing $inn then pressing Ctrl+P will 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+P repeatedly cycles through different previously-used words that ca