in reply to Re: strict, scope, my and foreach - not behaving as expected
in thread strict, scope, my and foreach - not behaving as expected

The difference is no one is going to be adding on to the pyramids and even if they did the proper equipment could be used for the additional construction.

New functionality may need to be added to the existing program, strict can help in that department but you would need it for the entire program. Plus just becase a program works doesn't mean it doesn't have bugs that could be caught by adding strict

Everyone would be much better off if coders stopped writting code that "works" and instead started writting code that works well, scales, and is easy to maintain. Of course, since we are talking about humans, that's not too likely to happen soon :)

Replies are listed 'Best First'.
Re: strict, scope, my and foreach - not behaving as expected
by Abigail-II (Bishop) on Jun 09, 2004 at 16:58 UTC
    Yeah, the keyword here being additional construction. The OP wasn't talking about extending a program. He was adding strict for the sake of adding strict.
    New functionality may need to be added to the existing program
    Yes, but why spend time now for something that may not happen? It's not that if a program remains stable for another year, that you have to hit the keyboard harder if you are going to add strict in a year, when you do modify the program.
    strict can help in that department but you would need it for the entire program.
    Sillyness. use strict is lexically scoped.
    Everyone would be much better off if coders stopped writting code that "works" and instead started writting code that works well, scales, and is easy to maintain.
    Totally beside the point. The program has already been written. Besides, just slapping a 'use strict' on the program isn't magical wand. Writing easy to maintain programs that scale well takes a lot more than slapping 'use strict' on the program. In fact, there isn't much relation between them.

    Abigail

      Yes, but why spend time now for something that may not happen?

      I agree. Now that you said that I just had to dig up this fine link that I like to give to my coworkers whenever they worry about what might happen down the road: you aren't gonna need it.

      -- vek --
        great link! vek++