Steve Simmons <[EMAIL PROTECTED]> writes: > For deprecation, we should have a %PERL_DEPRECATED{mod}{thing} hash as > well. `mod' is `CORE', `FORMATS', etc, as above. A value of 0 means the > function is actually gone, 1 means it's disappearing next major release, > 2 mean next minor, etc. The programmer can control what happens when > the feature is used by setting a %PERL_DEPRECATED{mod}{warning} value > to 0 for default, 1 for once, 2 for never, etc, etc. I *LIKE* this. Especically if a module author can do: BEGIN { @PERL_DEPRECATED{__PACKAGE__}{@deplist} = (1) x @deplist; @PERL_DEPRECATED{warnings}{__PACKAGE__}{@deplist} = (1) x @deplist; } -- Piers
- Removing/fixing $[line noise here] variables Steve Simmons
- Re: Removing/fixing $[line noise here] variables Nathan Torkington
- Re: Removing/fixing $[line noise here] variab... John Porter
- Re: Removing/fixing $[line noise here] variables Alan Burlison
- Re: Removing/fixing $[line noise here] variab... Nathan Wiger
- Re: Removing/fixing $[line noise here] va... Dan Sugalski
- Re: Removing/fixing $[line noise here] va... Steve Simmons
- RE: Removing/fixing $[line noise here] variables Piers Cawley
- RE: Removing/fixing $[line noise here] variables Brust, Corwin
- RE: Removing/fixing $[line noise here] variab... Dan Sugalski
- Re: Removing/fixing $[line noise here] va... Steve Simmons
- Re: Removing/fixing $[line noise here... Dan Sugalski
- Re: Removing/fixing $[line noise here... Larry Wall
- Re: Removing/fixing $[line noise... J. David Blackstone
- RE: Removing/fixing $[line noise here] variables Brust, Corwin
- RE: Removing/fixing $[line noise here] variables Brust, Corwin
- Re: Removing/fixing $[line noise here] variab... John Porter
- Re: Removing/fixing $[line noise here] va... Tom Christiansen