Perhaps you're still better off renaming the module, here's why.

Perl loads every module only once, see %INC in perlvar. So, if English is used internally by some other module down the road (which is likely, because it's 2012 and punctuation variables smell), it will not be loaded again. Instead, your module's import method will be called.

But use English; exports a lot of stuff into the calling package, like $ERRNO etc. And suddenly a random module not even used directly by the code you control breaks with a syntax error message!

Here's a little demo (run it as far as possible from your real English.pm!). Note the "not permitted" part is as planned (not a real error). The "echo 1" comand creates a correct empty module.

-bash$ rm English.pm 
-bash$ perl -Mstrict -I. -wle 'use English; $ERRNO=1; print $ERRNO; '
Operation not permitted
-bash$ echo 1 > English.pm
-bash$ perl -Mstrict -I. -wle 'use English; $ERRNO=1; print $ERRNO; '
Global symbol "$ERRNO" requires explicit package name at -e line 1.
Global symbol "$ERRNO" requires explicit package name at -e line 1.
Execution of -e aborted due to compilation errors.
[download]