> -----Original Message----- > From: Paul M Foster [mailto:paulf@xxxxxxxxxxxxxxxxx] > Sent: Thursday, January 29, 2009 8:02 PM > To: php-general@xxxxxxxxxxxxx > Subject: Re: Re: Hidden costs of PHP arrays? > > On Fri, Jan 30, 2009 at 11:10:16AM +1100, Clancy wrote: > > <snip> > > > As a former assembly language programmer I have some idea of the vast > > amount of thumb > > twiddling which is going on behind-the-scenes when I make some > apparently > > simple request > > like the one to get my phone number. Undoubtedly most of this occurs > in > > the murky depths > > of the operating system, but if there were any simple way to avoid > adding > > to it > > unnecessarily it would be nice to know about it. > > Ahhh, finally someone who understands this principle. There's simply no > reason to waste cycles if you don't have to. If that's REALLY your bag, just plot all of your functions in Assembly, first! https://www.scriptlance.com/cgi-bin/freelancers/project.cgi?id=121743701 3&order=bid%20DESC I, for one, will keep efficiency in mind--but if I spend a couple extra cycles to relieve myself of an extra 20 lines of code, I think I'll sleep just fine. :) Now, if I was programming embedded systems or time-critical transaction processing software, that might be another story. (Then again, if that were the case, I might not be playing with an interpreted language to begin with.) My 2c. // Todd -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
