in reply to Re: Making strict optional
in thread Making strict optional

Seeing how strict is lexically scoped using it inside of an eval inside of a BEGIN block's scope isn't really going to do the rest of one's code much good . . .

Replies are listed 'Best First'.
Re^3: Making strict optional
by gellyfish (Monsignor) on May 31, 2006 at 15:11 UTC

    Well you might say that:

    BEGIN { eval { require strict; }; strict->import() unless $@; } + $foo = 1;
    Gives rise to:
    Global symbol "$foo" requires explicit package name at hdhd line 10. Execution of hdhd aborted due to compilation errors.
    So no it does work. Update: but of course the string eval is different.

    /J\