in reply to Re: Re: Can't get the right array value
in thread Can't get the right array value

Aw, shucks... I didn't meen to make you feel stupid.

And if you're using a perl editor that can tell you when you make a mistake by 'misnaming' an undefined variable, lemme know what it is, I'd like to use it. My most common coding mistake is failing to type var names correctly.
One could argue that I should use simpler var names or put all vars and their description at the top of the closure, but while I've never been known as a lazy documenter, I usually only add comments to my code when I'm doing something that is odd or to explain a funky regex.

And strict is something you want to use always. Among other things, it forces you to declare your variable names before using them.

It'll save you time when you debug during development.

As for -w, well once you understand why you should use it, then you know when you can not use it. IMHO, all people in the early stages of perl should use warnings. Once you become more experienced you prolly wont use it as much, if at all.

$0.02 doesn't go as far as it used to, does it?

Replies are listed 'Best First'.
Re: Re: Re: Re: Can't get the right array value
by DaWolf (Curate) on Nov 08, 2001 at 01:12 UTC
    hehehe nevermind, XP. I woke up with the left foot today.

    The editor I use is Activestate Komodo. It's very cool, since it works with the perl interpreter and uses a "Micro$oft Word-like correction as you type". This is VERY useful, since it underlines a variable name if you mispelled or "used it only once".

    I think it will help you. : )

    It has one or two features missing like word wrap, but it should be on the next version of it.

    Oh, it also requires a lot of RAM (128Mb), but I assure you is worthy.

    Let me tell what you think about it.

    Best regards,

    Er Galvão Abbott
    a.k.a. Lobo, DaWolf
    Webdeveloper