On Fri, 25 Dec 2009, Jonathan Swartz wrote:
- $m->flush_buffer is now ignored when inside $m->scomp or $m->content.
Patch
by Frédéric Brière, with extra tests from Ruslan Zakirov. RT #38924.
I don't understand. In 1.29_01 we made this change:
- ** The behaviors of $m->flush_buffer and $m->clear_buffer have been
simplified. $m->flush_buffer only acts on the top-level output buffer;
$m->clear_buffer clears all output buffers. Task id #554.
That is, regardless of where $m->flush_buffer is called, it is supposed to
flush the top-level output buffer. Has this changed now?
There were some tests that went along with the patch I applied.
Basically, flushing inside a call to $m->content caused the output to be
sent out of order:
<&| foo.mas &><& flushes.mas &></&>
When flushes.mas calls $m->flush_buffer, its output "escapes" the confines
of the call to $m->content in foo.mas, so it ends up coming before the
output from foo.mas.
That just can't be right.
Take a look at the tests in t/25-flush-in-content.t for an example.
-dave
/*============================================================
http://VegGuide.org http://blog.urth.org
Your guide to all that's veg House Absolute(ly Pointless)
============================================================*/
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
