Re: PATCH: debug_backtrace() function for 4.3-dev/ZE1

[..] >> >Besides whos to say that >> >adding debug_backtrace now to 4.3 won't steer more people to php >> instead of other envrionments. >> >> I'm willing to be the first person to say this if no one beats me to >> it... Such a featurelet steering people to choose one >> technology/platform over the other? > > In one case ive heard someone didn't choose php becuase it doesn't > support MI. > Now ive heard this from a "not very smart programmer" but that was the > decision. I know that thats absoulty obsurde but something like php > doesn't support backtraces may or maynot lean someone twards php. I konw > this isn't the majority but maybe a handfull. Ive taken systems which I would have prefered to have done in PHP away from PHP (in that case I moved to Java for the stack tracing - because the code was used so much inside itself it was impossible to bug trace - especialy when the code was evaling heh). PHP is my forte and I would have prefered to do it with the language I know best and love. However - purely based on not having a backtrace I had to move. NOTE: At the time I was unaware of the existance of anything that could be plugged into PHP to do this... and this was 5 months ago. However, regardless of time frame - fact is that I moved because of the lack of a feature... one that is availiable to us, but were not putting in out of politics. [..] > Obvisouly we all have our own opnion I wanted to state mine not get in > a big > argument about this. I do see your point, as a zend2 advocate, and im > sure you see mine too, as a php user who wants debug_backtrace. So what > to do, do you just call the shots or do we have an offical vote? If there is a vote, Im +1 on the idea of a backtrace into the earliest PHP release possible. -- Dan Hardiker [dhardiker@staff.firstcreative.net] ADAM Software & Systems Engineer First Creative Ltd