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?)
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
On 20 Jun 2009, at 15:32, Jesse Sheidlower wrote:
I'm having a hell of a time trying to track down the reasons
for this error.
I'm getting an error that looks like:
Use of uninitialized value $buffer in concatenation (.) or
string at /usr/share/perl5/Catalyst/Engine/CGI.pm line 220.
For
On 26 Jun 2009, at 17:06, Merlyn Kline wrote:
being. Basically, though, the obvious proximal cause of this
would be
calling the write method with no parameter. This might seem an
[snip]
I'm afraid this isn't too helpful for me at least; in this
case I'm just an end user, not doing
On Mon, Jun 22, 2009 at 10:18:40AM +0100, Merlyn Kline wrote:
I'm getting an error that looks like:
Use of uninitialized value $buffer in concatenation (.) or
string at /usr/share/perl5/Catalyst/Engine/CGI.pm line 220.
Deep in my job list I have some notes surrounding this issue saying
being. Basically, though, the obvious proximal cause of this would be
calling the write method with no parameter. This might seem an
[snip]
I'm afraid this isn't too helpful for me at least; in this
case I'm just an end user, not doing anything fancy here, so
Presumably you *aren't*, in
I'm getting an error that looks like:
Use of uninitialized value $buffer in concatenation (.) or
string at /usr/share/perl5/Catalyst/Engine/CGI.pm line 220.
Deep in my job list I have some notes surrounding this issue saying that I
need to investigate further and possibly submit a patch or
