On Mon, May 05, 2008 at 03:46:09PM -0500, Jonathan Rockway wrote:
> * On Mon, May 05 2008, Daniel McBrearty wrote:
> > tht's reasonable.
> >
> > what is not so reasonable is suddenly deciding that you are going to
> > *croak* on something which you didn't even test for with previous
> > releases.
> >
> > A warning would have been fine, at least for half a year or so.
>
> In that case we would be having this exact discussion 6 months from
> now. Breaking broken code is always good. +1 for HTTP::Message.
Not when you're that far down the dependency chain.
Anyway, this thread was started to try and help get the fallout fixed,
not for you to posture. Either write code, shut up, or start a separate
thread so I can safely killfile it.
--
Matt S Trout Need help with your Catalyst or DBIx::Class project?
Technical Director http://www.shadowcat.co.uk/catalyst/
Shadowcat Systems Ltd. Want a managed development or deployment platform?
http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/servers/
_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
