what happens if you need to deprecate it ... ?
(I'm only half joking ... )
On 1/3/07, Robert 'phaylon' Sedlacek <[EMAIL PROTECTED]> wrote:
Matthieu Codron wrote:
> On 1/2/07, Joe Landman <[EMAIL PROTECTED]> wrote:
>
>> Might be a good thing to have an MODULES_CURRENT/MODULES_OBSOLETE list,
>> or ask the module authors to simply note the obsolescence in an updated
>> POD.
>
> I think it is a terrific idea.
> Catalyst is a lot about choice and flexibility, but reading the list makes
> me really think that there are good choices, bad choices, and even good
> ones that become bad.
I remember an effort for making a DeprecatedPlugins Plugin, but I don't
know where that stands. A plugin emmitting warnings based on a list in
the module (deprecated modules and replacements, specific versions, etc)
sounds easier to manage and keep up-to-date than a wiki page.
--
# Robert 'phaylon' Sedlacek
# Perl 5/Catalyst Developer in Hamburg, Germany
{ EMail => ' [EMAIL PROTECTED] ', Web => ' http://474.at ' }
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
--
Daniel McBrearty
email : danielmcbrearty at gmail.com
www.engoi.com : the multi - language vocab trainer
BTW : 0873928131
_______________________________________________
List: [email protected]
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
