Re: most powerful php editor
| From: | Richard Lynch | Date: | Fri, 26 Jan 2007 00:05:54 +0000 |
| Subject: | Re: most powerful php editor | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-247803@lists.php.net to get a copy of this message | ||
On Thu, January 25, 2007 3:06 am, Sancar Saran wrote:
> On Wednesday 24 January 2007 15:41, Roman Neuhauser wrote:
>> # sancar.saran@evodot.com / 2007-01-24 13:57:03 +0200:
>> > and also in these days I'm looking for 19 inch (or more) wide LCD
>> > sceerns to able to fit longer lines in my screen...
>>
>> Number of reading errors people make grows with line length,
>> this has been known for as long as I remember. You're increasing
>> the
>> probability of bugs in the code, and get tired sooner because
>> following
>> long lines requires more energy.
>
> Yes and no, because these days I'm obsessed very very large arrays
> like
>
> $arr['this']['is']['what']['i']['m']['looking']['for'];
>
> And If I start to do
>
> if(
> ($arr['this']['is']['what']['i']['m']['looking']['for']
> > 5) &&
>
> ($arr['this']['is']['what']['i']['m']['looking']['for']
> < 10))
>
> blah blah
>
> then problem begins :)
Get back to us after you get over your array obsession...
:-)
I rarely find myself using more than 2-D, or occasionally, 3-D array
lookups within any given section of code.
I *might* have deeper arrays, but I'm either going to recurse through
them, or break it down by what's actually in all those layers, and do
something different as I descend.
I would suggest that if one has data nested that deeply, perhaps the
stat structure itself is a poor choice. :-)
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?