in reply to Re: Why isn't C<use strict> the default?
in thread Why isn't C<use strict> the default?

This argument doesn't addresss the fact that one could arrange it so perl would turn on strict and warnings for code from any other source than -e but leave -e code unencumbered.


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi

    Flux8


  • Comment on Re^2: Why isn't C<use strict> the default?

Replies are listed 'Best First'.
Re^3: Why isn't C<use strict> the default?
by Aristotle (Chancellor) on Oct 29, 2004 at 08:20 UTC

    Or you could have another name for the binary that makes perl assume use strict; (and maybe warnings also)…

    #!/usr/bin/perls no swine;

    Makeshifts last the longest.