On Thu, 18 Jan 2007, Mark Elrod wrote: > Actually this issue came up when I reported a bug on SELF != > current_comp. John Williams wrote at that time: > > "The ability to use $m->call_next from a helper component is at least > assumed, since we have tests for it. I'm not sure if it is formally > documented anywhere, since it is not done very often. It probably never > worked correctly in the past. > > Using call_next from a helper component is tested for in t/11-inherit.t > (see the call_next_helper component in there). However the effect on the > request component is _not_ tested, since the <& variants &> component is > only called from /subdir/autohandler, and not from /subdir/normal. If you > add the call to <& variants &> to /subdir/normal, the problem is pretty > obvious, since the attributes and methods get invoked all wrong."
Ah, fascinating. Looking at revision control history, it seems like Jon Swartz added this test way back in 2000. Personally, I think this is wrong, but I'll let him make a definitive ruling that it should be supported if he wants to. Jon? -dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
