Yeah. We do. But I really want to get rid of all that reference shit for
1.0. We don't need to implicitly pass around objects as references anymore,
and we can just as well remove all the reference blah where it's just
dealing with normal variables but not changing them, likely because feti
didn't know about copy-on-change back then. I've already done some veeeery
minor cleanup in my view branch (getSlots() action changed), but I really
really really want to clean up everything. This implies a BC change, tho,
since subclasses need to implement the same signature (function &foo may not
extend function foo and vice versa)
Sure.. do it through tests though, it must be demonstrated that what you say is true. See, for example: http://trac.agavi.org/trac.cgi/file/trunk/tests/request/RequestTest.php After adding the tests to the request object that demonstrate a usefulness of passing around the values as references, I dont believe they should be removed in this particular case, the consequences are easy to study with the tests in place.
-Mike
Talking about rolling 0.10, anyway.. There's plenty more we can work on prior to 1.0.
_______________________________________________ agavi-dev mailing list [email protected] http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
