Popular posts

#1, agreed completely. Is it haystack, needle, or needle, haystack? php.net may be my most used site!!!

#2, I haven't really seen this as a problem in my work

#3, agreed I'll add to this...

#4, very poor garbage collection... can not have an infinite loop (e.g. queue system) that completely releases memory at the end of the loop. (If anyone has a way, PLEASE let me know.)

@jlcfly i like to separate the data structures from the interfaces who use them :) esp if they are real data structures like models but :D ... that's just taste I like lowlevel and like to define types and such. about 4 g yes GC is a bitch the trick is nulling at least was my way to handle memory problems because unset ,as you know, did not clean up an infinite loop :) for me it worked but i think it was php 5.2 where is had to use it for a Database State analysis tool in PHP not really sophisticated at the time but i learned at least that I had to null the sets to not run out of memory to fast :)

lol, your #1 is my #1. I have trouble with that E.V.E.R.Y time! Thankfully, VScode helps on that matter.

I would add the fact to have to add isset to check if an entry in an array exists before checking its value.

cedric simon you could just use @$data['entry'] it supresses the warning usually :).