Hello Andi, deep integration of reflection is good to be able to get as much information out of it as possible. On the other hand we're not java and have different code strategies and especially java's demand for reflection doesn't apply to php (dependency injection/inversion of control). And if i remember correctly it was you that kept me back from allowing that stuff. That said there is only two main reasons for refletion left. Helping during development and a very tiny edge case (something like dynamically creating objects). On the other hand reflection is a very big extension. So a few ppl might want to have their own php builds without reflection. That is also the reason why we lately came to agree on moving reflection into its own ext and even Zeev agreed.
best regards marcus Saturday, November 19, 2005, 2:49:09 AM, you wrote: > As I mentioned to Marcus, it seems odd to me to move reflection in > the first place. It seems to me to be very much a language feature > and in my opinion, should always be enabled. I can't really see a > good reason for this move. > Andi > At 07:40 AM 11/18/2005, Derick Rethans wrote: >>On Fri, 18 Nov 2005, Antony Dovgal wrote: >> >> > We need at least document it or to add something like this: >> >>But then we need to do this for every configure option... as nobody >>really knows what they are doing anyway. >> >>Derick >> >>-- >>Derick Rethans >>http://derickrethans.nl | http://ez.no | http://xdebug.org >> >>-- >>PHP CVS Mailing List (http://www.php.net/) >>To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
