On Fri, May 4, 2007 12:46 pm, Ilia Alshanetsky wrote: >>>> 2) Add open_filename debug info to streams >> >>> What would this mean for performance and memory usage of file ops? >> >> An additional malloc and strcpy on opening and an additional free >> on closing. We could however limit actual use to --enable-debug >> builds. > > My preference we enable this feature only for debug builds.
There might be users for whom debug info in production is way more important than raw performance... I dunno how expensive (malloc + strcopy + free) is, but it doesn't seem to this naive reader like it's going to swamp a server, if somebody who knows what they are doing wants that on even in production. I could easily be under-estimating the expense, but it just seems like there's a lot more PHP scripts that need a lot more better debugging code more than they need raw performance. I'm not claiming that having this available will stop any idiots from writing bad code, but it might help a couple smart folks write better code. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
