[PATCH] UNIVERSAL shouldn't require Exporter

Historical accident fixed, in the hope that someone will tell me what
I'm missing. Was it merely an oversight that this wasn't fixed earlier,
or does somebody rely on the Exporter behaviour?

"These subroutines should NOT be imported via use UNIVERSAL qw(...)",
but would a patch which allowed this anyway (as Exporter does) be a
better idea? Or do we need an import at all?

- ams

--- perl@9818/lib/UNIVERSAL.pm~	Thu Apr 26 03:14:28 2001
+++ perl@9818/lib/UNIVERSAL.pm	Thu Apr 26 03:30:44 2001
@@ -2,12 +2,7 @@
 
 our $VERSION = '1.00';
 
-# UNIVERSAL should not contain any extra subs/methods beyond those
-# that it exists to define. The use of Exporter below is a historical
-# accident that should be fixed sometime.
-require Exporter;
-*import = \&Exporter::import;
-@EXPORT_OK = qw(isa can);
+sub import { }
 
 1;
 __END__

• [PATCH] UNIVERSAL shouldn't require Exporter by Abhijit Menon-Sen
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Mike Guy
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Jarkko Hietaniemi
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Mike Guy
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Simon Cozens
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Graham Barr
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Mike Guy
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Mike Guy
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Benjamin Sugars
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Graham Barr
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by barries
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Abhijit Menon-Sen
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Graham Barr
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Simon Cozens
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Graham Barr
• Re: [PATCH] UNIVERSAL shouldn't require Exporter by Graham Barr