in reply to RE: RE: RE: RE: new module idea
in thread new module idea

> >there's no real need to keep use strict turned on

>IMO, that isn't good practice, just leave it on. There are two camps on this but when
> you look at the majority of modules on the CPAN, strict is on and IMO should be left
> on. If I see a module with it commented out I wonder why.

I agree - short simple scripts don't need strict but when you have something large, and especially something like a module which may be used by others than yourselves, add the use strict. If it really bothers you, you can always turn it off with a no strict (this is sometimes even necessary) but it is better to make no strict the exception, rather than the rule.

Replies are listed 'Best First'.
RE: RE: RE: RE: RE: RE: new module idea
by jimt (Chaplain) on Aug 15, 2000 at 01:11 UTC
    It's still simply a stylistic question.

    As I said, the module was developed with 'use strict' enabled. It's should behave perfectly fine with use strict turned on or not, I'm just leaving it up to the end user instead of forcing it on them.

    I will continue to view 'use strict' as a developer tool. It's something to aid in catching "bad" code and "bad" practices while developing, but after a piece of code is done, no development is going on and hence it's not really needed. It does add a slight performance hit (though it is almost negligible, I'll admit).

    Besides, there are far too many modules on CPAN that do not behave properly with 'use strict' to really argue over the merits of actually keeping it enabled or not in a submitted module. As long as it was written so that it behaves with use strict and/or $^W, I really don't care.