On Thu, 2005-11-17 at 18:51, Robert Cummings wrote:
> On Thu, 2005-11-17 at 18:33, Ilia Alshanetsky wrote:
> > Andreas Korthaus wrote:
> > > OK, but by dropping {} for strings you also remove the possibility to
> > > have a convention like "[] for arrays and {} for strings".
> > > If I could decide I would drop {} for arrays and [] for strings, but I
> > > fear I will not be asked to decide... ;-)
> >
> > You may think that {} and [] are different, but in reality same code
> > deals with both. Having two constructs for the same behavior is silly
> > and leads to confusing, hard to read code. Especially so when you
> > consider the fact {} has another meaning that is completely different.
>
> That should have been considered before everyone was told that [] was
> deprecated for strings in favour of {}. Dropping support for string
> access via {} is akin to slapping those who followed the lead. Once
> bitten, twice shy. I don't see support for <? being dropped anytime, yet
> it falls under the exact same argument. But maybe there's a trend
> emerging here, and in fact <?php will be deprecated in the near future.
> It's a tough call since credibility is rapidly swirling down the toilet.
I just re-read what I posted, and it's a bit meaner sounding than I
intended, but I'm sure you can understand the mounting frustration :|
Cheers,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com |
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
