Re: [PATCH] UNIVERSAL shouldn't require Exporter

On Thu, 26 Apr 2001, Mike Guy wrote:

> But as Graham has pointed out, we can't withdraw it without going through
> a deprecation cycle first.    And mending perlobj.pod.  :-(

Since you've just fixed perlobj.pod, should we go ahead and deprecate it
for 5.8?

Cheers,
-Ben

-- 
signer: can't create ~/.sig: Resource temporarily unavailable

• [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 Benjamin Sugars
• 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 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