Deprecation cycle

[Andy Armstrong]

On 22 Jun 2008, at 10:23, Steve Purkis wrote:
> I've just written this in the HACKING.pod -- seems sensible to me,
> though I'm not sure if everyone agrees with it:
>
> ------------------
> =head1 Deprecation cycle
>
> Any I<documented> sub that needs to be changed or removed (and would
> therefore
> cause a backwards-compat issue) must go through a deprecation cycle
> to give
> developers a chance to adjust:


Yeah, that's sensible in general. We should probably make 'em carp a  
suitable message too.

I suspect that in the case of your orphaned error / exit we can just  
drop them though.

-- 
Andy Armstrong, Hexten