On 1 Jul 2009, at 10:11, Merlyn Kline wrote:
>> What are people's thoughts about adding a specific warning if you try
>> to write undef? (As you could still cause this warning by doing that
>> explicitly)
>
> Depends why you might do this - if it's legitimate (e.g. to force the
> headers to be flushed?) then it should be handled silently.
> Otherwise, a
> warning would seem sensible.
Yeah, it totally is sane, for just that reason, and the warning is in
Engine::HTTP (so the dev server), but not in other engines..
http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=10864Fixed!
Cheers
t0m
_______________________________________________
List:
Catalyst@...
Listinfo:
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalystSearchable archive:
http://www.mail-archive.com/catalyst@.../Dev site:
http://dev.catalyst.perl.org/
