missing `import' method is an error?

[Mark-Jason Dominus <mjd@plover.com>]

Someone pointed out in comp.lang.perl.misc that the `perlfunc' man
page says, under `use':

	If no C<import()> method can be found then the error is
	currently silently ignored.  This may change to a fatal error
	in a future version.

He pointed out that changing this to a fatal error would break lots
and lots of modules, including all those that are not intended to
export anything, but rather to provide a collection of methods.

I don't know what this clause is there for, but perhaps it should be
removed.  In case that is the outcome, I have enclosed a patch.


Mark-Jason Dominus 	  			                 mjd@plover.com
I am boycotting Amazon. See http://www.plover.com/~mjd/amazon.html for details.


--- pod/perlfunc.pod	2000/01/27 14:08:21	1.2
+++ pod/perlfunc.pod	2000/01/27 14:08:58
@@ -5066,8 +5066,7 @@
 C<import> method any way it likes, though most modules just choose to
 derive their C<import> method via inheritance from the C<Exporter> class that
 is defined in the C<Exporter> module.  See L<Exporter>.  If no C<import>
-method can be found then the error is currently silently ignored.  This
-may change to a fatal error in a future version.
+method can be found then the error is silently ignored.  
 
 If you don't want your namespace altered, explicitly supply an empty list:

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---