Re: summarizing the obvious (was: arrays, hashes unified ...)

2003-02-02 Thread Sam Vilain
On Sat, 01 Feb 2003 06:40, Garrett Goebel wrote: > Or for the extremely thick: > GOOD: Separate syntax for indexed vs. named lookups > BAD: Same syntax with >= 2 contextual meanings Or, another way to look at it; GOOD: flexible, re-usable code that doesn't care if you change the key type

out-of-place-rant (was: summarizing the obvious)

2003-01-31 Thread Garrett Goebel
Michael Lazzaro wrote: > On Friday, January 31, 2003, at 09:40 AM, Garrett Goebel wrote: > > > > > > I'm disappointed that The Perl Foundation (TPF) has been so > > quiet and unresponsive on support for our core language > > designers and architects. I dropped a note to all the TPF > > contacts

Re: summarizing the obvious

2003-01-31 Thread Michael Lazzaro
On Friday, January 31, 2003, at 09:40 AM, Garrett Goebel wrote: Or for the extremely thick: GOOD: Separate syntax for indexed vs. named lookups BAD: Same syntax with >= 2 contextual meanings Seriously, everyone read Damian's "Seven Deadly Sins" thing, if ya haven't read/heard it already.

summarizing the obvious (was: arrays, hashes unified ...)

2003-01-31 Thread Garrett Goebel
From: Piers Cawley [mailto:[EMAIL PROTECTED]] > Garrett Goebel <[EMAIL PROTECTED]> writes: > > > > $idx_of_foo = $queue['foo']; # named lookup > > $nth_foo= $queue[600]; # ordered lookup > > > > One is SvPOK the other SvIOK... > > > > Can't we handle both and still have the ordered lookup be