Re: 1.3101 headers output after error on compilation error

On Fri, 9 Sep 2005, Gareth Kirwan wrote:

> I tried tracking down how or where the error is being output before the
> headers, but couldn't track it down.
> Mason::Exception's new returns $self, and at that point the error hasn't be
> output yet.
> Yet the only thing that happens after that is that Exception::Class dies on
> the return.
>
> I've been looking at a working Mason 1.27, Exception::Class 1.15 system, and
> trying to work out how the headers get output first there, but can't see it.
> Mason::Exception's new returns $self the same, and it just has the error
> html in it, not the header, and Exception::Class dies at that point the
> same.
>
> Any idea what might be causing this or where I should look next?

Can you give us a simple reproduction recipe?  If I can reproduce it I'd 
be inclined to fix it and make a new release, since it's a non-trivial 
bug.


-dave

/*===================================================
VegGuide.Org                        www.BookIRead.com
Your guide to all that's veg.       My book blog
===================================================*/


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf