in reply to "use strict" not too strict

A trivial work around is to create a script like so:
my $file = shift or die "USAGE: $0 [file]\n"; open CODE, $file or die "can't read $file: $!"; my $code = do {local $/;<CODE>}; eval $code; warn $@ if $@;
I haven't tested the robustness of this (nor am i going to as i feel using Test suites is the better solution), but this will work with your small example. And tell your cow-orker that C won't let you do a lot of stuff that Perl will! :P

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Replies are listed 'Best First'.
Re: (jeffa) Re: "use strict" not too strict
by bobn (Chaplain) on Jul 15, 2003 at 15:26 UTC

    The problem with this is that if the undefined sub is in a branch that does not get executed in the envronment you have created, it will still not be caught.

    if (0) { undefined_sub(); # no error even at runtime } else { undefined_sub2(); # error here }
    --Bob Niederman, http://bob-n.com