Actually, this one was prompted by seeing a bug fix or changelog about
requiring { } and : endif; to match up, rather than accepting
either/or in balance.
Synchronicity that I even saw that item, but there it is.
I would HOPE that they'd have to balance, but if they don't for the
long block syntax instead of braces, maybe they shouldn't.
Once you have two ways to delimit start and end, you ought to nail
down what does or doesn't work.
The Regex thing with < and > for start/end delimiters is also a
counter-example of what other people seem to like.
I prefer not to take things for granted when defining new syntax,
personally.
On Tue, February 6, 2007 11:28 am, Andrei Zmievski wrote:
> Now you're just grandstanding.
>
> -Andrei
>
>
> On Feb 5, 2007, at 3:55 PM, Richard Lynch wrote:
>
>> More edge cases:
>>
>> $foo = array(1, 2, 3];
>> $bar = [1, 2, 3);
>>
>> Syntax error because it's unbalancedO
>>
>> Or kosher, because the choice of start/end delimiters should be up
>> to
>> the user?
>>
>> Should it match whatever rule is in place for:
>>
>> if (...){
>> endif;
>>
>>
>>
>> --
>> 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?
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
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?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
