[PHP-DEV] GOTO and/or BREAK LABEL
Hi, Because of some confused people I reverted "break label" patch and post it for discussion once again together with GOTO patch. Please reviw and vote. 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing My vote: (1) +0.5, (4) +0.5 Thanks. Dmitry. tests.tar.gz Description: GNU Zip compressed data -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 7 Mar 2006, Dmitry Stogov wrote: > Hi, > > Because of some confused people I reverted "break label" patch and post it > for discussion once again together with GOTO patch. > > Please reviw and vote. > > 1) goto and break label > 2) goto only (like C) > 3) break label only (like Java) > 4) nothing 5) goto, fowarding-jumping only. - Sascha -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Dmitry Stogov wrote: > Please reviw and vote. > > 1) goto and break label > 2) goto only (like C) > 3) break label only (like Java) > 4) nothing 1) +1 Edin -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
DS>>1) goto and break label DS>>2) goto only (like C) DS>>3) break label only (like Java) DS>>4) nothing 1) +0.5 2) -1 3) +1 -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 7 Mar 2006, Sascha Schumann wrote: > On Tue, 7 Mar 2006, Dmitry Stogov wrote: > > > Hi, > > > > Because of some confused people I reverted "break label" patch and post it > > for discussion once again together with GOTO patch. > > > > Please reviw and vote. > > > > 1) goto and break label > > 2) goto only (like C) > > 3) break label only (like Java) > > 4) nothing > > 5) goto, fowarding-jumping only. Yes I agree with that if you mean by forwarding: down and out of scope only (not into loop constructs). I would assume you mean that though. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 07.03.2006 11:28, Dmitry Stogov wrote: Hi, Because of some confused people I reverted "break label" patch and post it for discussion once again together with GOTO patch. Please reviw and vote. 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing 2) +0.5 4) +0.5 -- Wbr, Antony Dovgal -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 3/7/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: > 1) goto and break label +1 I'm happy with goto, but don't mind getting labelled breaks "for free"; labels are better than numbers. > 2) goto only (like C) +1 > 3) break label only (like Java) +0.5, but only if we don't have goto --Wez. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 3/7/06, Wez Furlong <[EMAIL PROTECTED]> wrote: > On 3/7/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: > > 1) goto and break label > +1 > > I'm happy with goto, but don't mind getting labelled breaks "for > free"; labels are better than numbers. same here +1 > > 2) goto only (like C) +1 > > 3) break label only (like Java) > +0.5, but only if we don't have goto +0 --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
At 11:28 07/03/2006, Dmitry Stogov wrote: Hi, Because of some confused people I reverted "break label" patch and post it for discussion once again together with GOTO patch. Please reviw and vote. 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing My vote: (1) +0.5, (4) +0.5 (3) +0.5 (4) +1 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 3/7/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Because of some confused people I reverted "break label" patch and post it
> for discussion once again together with GOTO patch.
>
> Please reviw and vote.
>
> 1) goto and break label
> 2) goto only (like C)
> 3) break label only (like Java)
> 4) nothing
>
thanks for this thread.
+0.5 for goto
+1 for "do { break label; } while(0); label:" (line label, same with goto)
or if the above is not acceptable, +0.5 for java like "label: do {
break label; } while(0);" (block label, confusing with goto)
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Sascha Schumann wrote: 5) goto, fowarding-jumping only. which would more or less make it useless for state machine stuff, right? -- Hartmut Holzgraefe, Senior Support Engineer. MySQL AB, www.mysql.com Join me at MySQL's 2006 Users Conference, April 24-27! http://www.mysqluc.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Dmitry Stogov wrote: 1) goto and break label +1 2) goto only (like C) +1 3) break label only (like Java) -1 Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing Thanks for giving this a final chance, Dmitry. 1) +0.5 3) +1 - Steph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
I'm with Rasmus on the break label stuff. Although it's not confusing to me, I got convinced quickly that it'll be confusing to the wider audience. So big -1 from me for (2) & (1). I think we should either stick with nothing or go to a full goto (without jumping into scopes of course). Only forward gotos would go against one of the main initial motivations for discussing this which was state machines. I suggest we apply this and allow people to play around with it/test it Btw, how about naming it "jump" and not "goto"? :) Andi At 01:28 AM 3/7/2006, Dmitry Stogov wrote: Hi, Because of some confused people I reverted "break label" patch and post it for discussion once again together with GOTO patch. Please reviw and vote. 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing My vote: (1) +0.5, (4) +0.5 Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Andi Gutmans wrote: > I'm with Rasmus on the break label stuff. Although it's not confusing to > me, I got convinced quickly that it'll be confusing to the wider > audience. So big -1 from me for (2) & (1). >From your comment bellow I figure you're for option 2, right? Edin > I think we should either stick with nothing or go to a full goto > (without jumping into scopes of course). Only forward gotos would go > against one of the main initial motivations for discussing this which > was state machines. > > I suggest we apply this and allow people to play around with it/test it > > Btw, how about naming it "jump" and not "goto"? :) > Andi > > At 01:28 AM 3/7/2006, Dmitry Stogov wrote: > >> Hi, >> >> Because of some confused people I reverted "break label" patch and >> post it >> for discussion once again together with GOTO patch. >> >> Please reviw and vote. >> >> 1) goto and break label >> 2) goto only (like C) >> 3) break label only (like Java) >> 4) nothing >> >> My vote: (1) +0.5, (4) +0.5 >> >> Thanks. Dmitry. >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Yes 2. Sorrry At 07:28 AM 3/7/2006, Edin Kadribasic wrote: Andi Gutmans wrote: > I'm with Rasmus on the break label stuff. Although it's not confusing to > me, I got convinced quickly that it'll be confusing to the wider > audience. So big -1 from me for (2) & (1). >From your comment bellow I figure you're for option 2, right? Edin > I think we should either stick with nothing or go to a full goto > (without jumping into scopes of course). Only forward gotos would go > against one of the main initial motivations for discussing this which > was state machines. > > I suggest we apply this and allow people to play around with it/test it > > Btw, how about naming it "jump" and not "goto"? :) > Andi > > At 01:28 AM 3/7/2006, Dmitry Stogov wrote: > >> Hi, >> >> Because of some confused people I reverted "break label" patch and >> post it >> for discussion once again together with GOTO patch. >> >> Please reviw and vote. >> >> 1) goto and break label >> 2) goto only (like C) >> 3) break label only (like Java) >> 4) nothing >> >> My vote: (1) +0.5, (4) +0.5 >> >> Thanks. Dmitry. >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Dmitry Stogov wrote: 1) goto and break label +0.5 2) goto only (like C) +1 3) break label only (like Java) -1 Rob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 2006-03-07 at 12:28 +0300, Dmitry Stogov wrote: > Hi, > > Because of some confused people I reverted "break label" patch and post it > for discussion once again together with GOTO patch. > > Please reviw and vote. > > 1) goto and break label > 2) goto only (like C) > 3) break label only (like Java) > 4) nothing > > My vote: (1) +0.5, (4) +0.5 > > Thanks. Dmitry. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php 1) +0 2) +1 3) -1 4) -1 I personally think labelled breaks are more fluff than anything. Like Greg I just haven't seen any examples of trying to break out of more than 3 loops in live code and I only recall seeing that once. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Hi, On Tuesday 07 March 2006 10:28, Dmitry Stogov wrote: > 1) goto and break label +1 > 2) goto only (like C) +1 > 3) break label only (like Java) -1 > 4) nothing -1 Regards, Magnus "Currently 'a bit' inactive" Määttä -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
(2) +1e10 On Mar 7, 2006, at 1:28 AM, Dmitry Stogov wrote: Hi, Because of some confused people I reverted "break label" patch and post it for discussion once again together with GOTO patch. Please reviw and vote. 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing My vote: (1) +0.5, (4) +0.5 Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote: > Hi, > > Because of some confused people I reverted "break label" patch and post it > for discussion once again together with GOTO patch. > > Please reviw and vote. > > 1) goto and break label > 2) goto only (like C) > 3) break label only (like Java) > 4) nothing 2) +1 What's the policy on voting btw? Am I allowed? 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
Re: [PHP-DEV] GOTO and/or BREAK LABEL
At 09:50 AM 3/7/2006, Robert Cummings wrote: On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote: > Hi, > > Because of some confused people I reverted "break label" patch and post it > for discussion once again together with GOTO patch. > > Please reviw and vote. > > 1) goto and break label > 2) goto only (like C) > 3) break label only (like Java) > 4) nothing 2) +1 What's the policy on voting btw? Am I allowed? Sure you can vote. Doesn't mean we'll listen to you though :) Andi -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 2006-03-07 at 12:50, Andi Gutmans wrote: > At 09:50 AM 3/7/2006, Robert Cummings wrote: > >On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote: > > > Hi, > > > > > > Because of some confused people I reverted "break label" patch and post it > > > for discussion once again together with GOTO patch. > > > > > > Please reviw and vote. > > > > > > 1) goto and break label > > > 2) goto only (like C) > > > 3) break label only (like Java) > > > 4) nothing > > > >2) +1 > > > >What's the policy on voting btw? Am I allowed? > > Sure you can vote. Doesn't mean we'll listen to you though :) That's better then nothing. At least I feel included ;) 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
Re: [PHP-DEV] GOTO and/or BREAK LABEL
if($choice == 1) {
goto bad;
} else if ($choice == 2) {
goto good;
} else if ($choice == 3) {
goto bad;
} else if ($choice == 4) {
goto good;
}
good:
$vote++;
bad:
return;
On Tue, 2006-03-07 at 12:50 -0500, Robert Cummings wrote:
> On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote:
> > Hi,
> >
> > Because of some confused people I reverted "break label" patch and post it
> > for discussion once again together with GOTO patch.
> >
> > Please reviw and vote.
> >
> > 1) goto and break label
> > 2) goto only (like C)
> > 3) break label only (like Java)
> > 4) nothing
>
> 2) +1
>
> What's the policy on voting btw? Am I allowed?
>
> 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
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 2006-03-07 at 12:58, John Coggeshall wrote:
> if($choice == 1) {
> goto bad;
> } else if ($choice == 2) {
> goto good;
> } else if ($choice == 3) {
> goto bad;
> } else if ($choice == 4) {
> goto good;
> }
>
> good:
> $vote++;
> bad:
> return;
I don't remember, but I think Sarah Golemon allowed for it in one of her
patches way back:
'bad',
2 => 'good',
3 => 'bad',
4 => 'acceptable',
);
goto $map[$choice];
good:
vote += .5;
acceptable:
vote += .5;
bad:
return;
?>
For the record, I wouldn't normally fall through like that, but we're
just having fun :B
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
Re: [PHP-DEV] GOTO and/or BREAK LABEL
I took that as (2) +1, (4) +1.
Current raw totals amongst those who contribute to the PHP core: (1) +5.5,
(2) +9.5, (3) +0, (4) 2
Still to vote: Derick, Marcus, George, Sascha, Hartmut, Chregu, Johannes,
Sebastian, Stefan, apologies if I missed any names here.
Current raw totals amongst all votes: (1) +7.5, (2) +13, (3) +0.5, (4) 0
Still notably haven't heard from: Lukas, Nuno, Alan K, Sean...
- Original Message -
From: "John Coggeshall" <[EMAIL PROTECTED]>
To: "Robert Cummings" <[EMAIL PROTECTED]>
Cc: "Dmitry Stogov" <[EMAIL PROTECTED]>;
Sent: Tuesday, March 07, 2006 7:58 PM
Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL
if($choice == 1) {
goto bad;
} else if ($choice == 2) {
goto good;
} else if ($choice == 3) {
goto bad;
} else if ($choice == 4) {
goto good;
}
good:
$vote++;
bad:
return;
On Tue, 2006-03-07 at 12:50 -0500, Robert Cummings wrote:
On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote:
> Hi,
>
> Because of some confused people I reverted "break label" patch and post
> it
> for discussion once again together with GOTO patch.
>
> Please reviw and vote.
>
> 1) goto and break label
> 2) goto only (like C)
> 3) break label only (like Java)
> 4) nothing
2) +1
What's the policy on voting btw? Am I allowed?
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
__ NOD32 1.1380 (20060125) Information __
This message was checked by NOD32 antivirus system.
http://www.eset.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Hi, On Tuesday 07 March 2006 19:14, Robert Cummings wrote: > I don't remember, but I think Sarah Golemon allowed for it in one of her > patches way back: > > > $map = array > ( > 1 => 'bad', > 2 => 'good', > 3 => 'bad', > 4 => 'acceptable', > ); > > goto $map[$choice]; NOOO - If we add goto only with static labels. Everything else is a total mess. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
I don't remember, but I think Sarah Golemon allowed for it in one of her patches way back: goto $map[$choice]; Yes, and targeting dynamic labels was one of the first big sacrifices on the altar of compromise. Current implementation options use static, compile-time resolved labels only. -Sara (no h thank you) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Steph Fox wrote: > Still notably haven't heard from: Lukas, Nuno, Alan K, Sean... 1) 0 2) 0 3) 0 4) 0 Sorry for the noise. I was told to vote. I don't personally have much use for goto, and I see both sides. I also only run PHP on dedicated platforms, so if appropriate engine mods were made (if necessary), and goto went into PECL that would be best for me. S -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 7 Mar 2006, Steph Fox wrote: > I took that as (2) +1, (4) +1. > > Current raw totals amongst those who contribute to the PHP core: (1) +5.5, (2) > +9.5, (3) +0, (4) 2 > > Still to vote: Derick, Marcus, George, Sascha, Hartmut, Chregu, Johannes, > Sebastian, Stefan, apologies if I missed any names here. I think Sascha and I already did... anyway, I go: (1) -1 (2) +1 (3) -1 (4) -1 Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Hello Dmitry, Tuesday, March 7, 2006, 10:28:27 AM, you wrote: > Hi, > Because of some confused people I reverted "break label" patch and post it > for discussion once again together with GOTO patch. > Please reviw and vote. > 1) goto and break label -1e307 > 2) goto only (like C) -1e307 > 3) break label only (like Java) given usable non confusing syntax i am ok > 4) nothing +1 > My vote: (1) +0.5, (4) +0.5 "If i want Spaghetti i cook some and don't brew unreadable and unmaintainable php code. And if i write a parser or scanner i use C and only C and nothing else. And besides the latter there is need for the concept goto." And well i am ignoring the rest of this :-) Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On Tue, 2006-03-07 at 13:52, Sara Golemon wrote: > > I don't remember, but I think Sarah Golemon allowed for it in one of her > > patches way back: > > > > goto $map[$choice]; > > > Yes, and targeting dynamic labels was one of the first big sacrifices on the > altar of compromise. Current implementation options use static, > compile-time resolved labels only. Yeah I remember that too -- vaguely (it's been a long time). Still, dynamic labels were never very important IMHO. > -Sara (no h thank you) My apologies, my wife's name is Sarah so the 'h' just seems to flow :) 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
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Steph Fox wrote: Still to vote: Derick, Marcus, George, Sascha, Hartmut, Chregu, Johannes, Sebastian, Stefan, apologies if I missed any names here. 1) -1 2) +1 3) +.5 4) -0 -- Hartmut Holzgraefe, Senior Support Engineer. MySQL AB, www.mysql.com Join me at MySQL's 2006 Users Conference, April 24-27! http://www.mysqluc.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Hi, On Tuesday 07 March 2006 19:18, Steph Fox wrote: > Current raw totals amongst those who contribute to the PHP core: (1) +5.5, > (2) +9.5, (3) +0, (4) 2 > > Still to vote: Derick, Marcus, George, Sascha, Hartmut, Chregu, Johannes, > Sebastian, Stefan, apologies if I missed any names here. Alright, my vote: 1) -1 2) +1 3) -1 4) 0 johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
2) +1
Since I can see it's use, and I've already seen 101 ways to write
spagetti code, so 102 ways isnt much different ;)
Regards
Alan
Steph Fox wrote:
I took that as (2) +1, (4) +1.
Current raw totals amongst those who contribute to the PHP core: (1)
+5.5, (2) +9.5, (3) +0, (4) 2
Still to vote: Derick, Marcus, George, Sascha, Hartmut, Chregu,
Johannes, Sebastian, Stefan, apologies if I missed any names here.
Current raw totals amongst all votes: (1) +7.5, (2) +13, (3) +0.5, (4) 0
Still notably haven't heard from: Lukas, Nuno, Alan K, Sean...
- Original Message - From: "John Coggeshall"
<[EMAIL PROTECTED]>
To: "Robert Cummings" <[EMAIL PROTECTED]>
Cc: "Dmitry Stogov" <[EMAIL PROTECTED]>;
Sent: Tuesday, March 07, 2006 7:58 PM
Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL
if($choice == 1) {
goto bad;
} else if ($choice == 2) {
goto good;
} else if ($choice == 3) {
goto bad;
} else if ($choice == 4) {
goto good;
}
good:
$vote++;
bad:
return;
On Tue, 2006-03-07 at 12:50 -0500, Robert Cummings wrote:
On Tue, 2006-03-07 at 04:28, Dmitry Stogov wrote:
> Hi,
>
> Because of some confused people I reverted "break label" patch and
post > it
> for discussion once again together with GOTO patch.
>
> Please reviw and vote.
>
> 1) goto and break label
> 2) goto only (like C)
> 3) break label only (like Java)
> 4) nothing
2) +1
What's the policy on voting btw? Am I allowed?
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
__ NOD32 1.1380 (20060125) Information __
This message was checked by NOD32 antivirus system.
http://www.eset.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 7.3.2006 15:44 Uhr, Steph Fox wrote: 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing In Sean's words: 1) 0 2) 0 3) 0 4) 0 Sorry for the noise. I was told to vote. Meaning, I don't care, never had a use for GOTO, but if the caring majority thinks, it's needed, why not :) chregu -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 44 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | [EMAIL PROTECTED] | GPG 0x5CE1DECB -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Christian Stocker schrieb: > 1) 0 > 2) 0 > 3) 0 > 4) 0 > > Sorry for the noise. I was told to vote. > > Meaning, I don't care, never had a use for GOTO, but if the caring > majority thinks, it's needed, why not :) Same here. -- Sebastian Bergmann http://www.sebastian-bergmann.de/ GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 7.3.2006 15:44 Uhr, Steph Fox wrote: 1) goto and break label 2) goto only (like C) 3) break label only (like Java) 4) nothing Sorry for the noise. I was told to vote. Meaning, I don't care, never had a use for GOTO, but if the caring majority thinks, it's needed, why not :) chregu same here. 1) -1 2) 0.5 3) -1 4) 0 Nuno -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] GOTO and/or BREAK LABEL
On 07 March 2006 09:28, Dmitry Stogov wrote:
> Please reviw and vote.
>
> 1) goto and break label
> 2) goto only (like C)
> 3) break label only (like Java)
> 4) nothing
1) +0.25
2) -1e38
3) +1e38
4) -infinity
Or, in other words, I want labelled break, and I don't want to have to emulate
it with goto.
As a user who spent several *days* tracking down a subtle bug caused by a
continue n that hadn't been altered to continue n+1, I regard labelled break as
a vital addition -- for me, it's not the frequency with which it is used (very
low, I agree), but the incredibly disproportionate maintenance burden
(potentially extremely high). In my case, I was adding a level to a heavily
nested looping/conditional structure (7 or 8 levels deep) extending over
several hundred lines, and out of the few break/continue statements that needed
adjusting I missed just one. If they had been labelled breaks, there would
have been *no* maintenance problem, and I'd have had several more days on the
next step.
If the "Java-like" syntax is seen as confusing, what about, as in some other
languages, interpolating the label into the for/foreach/while statement:
for () label {...} or for label (...) {...}
This is clearly a different animal from a goto target label: (but should be in
the same namespace, of course).
OK, I'll shut up now and slope off into a corner. (Perhaps I should design my
own language whilst I'm there ... but nah, did that decades ago and got bored
-- prefer higher-level programming these days!)
Cheers!
Mike
-
Mike Ford, Electronic Information Services Adviser,
Learning Support Services, Learning & Information Services,
JG125, James Graham Building, Leeds Metropolitan University,
Headingley Campus, LEEDS, LS6 3QS, United Kingdom
Email: [EMAIL PROTECTED]
Tel: +44 113 283 2600 extn 4730 Fax: +44 113 283 3211
To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
> If the "Java-like" syntax is seen as confusing, what about, as in some other
> languages, interpolating the label into the for/foreach/while statement:
>
> for () label {...} or for label (...) {...}
a. label: for () { break label; } AND label: { for () {
break label; } } (see
http://www.rgagnon.com/javadetails/java-0500.html )
b. for () label { break label; }
c. for () { break label; } label:
ok, i was +1 for c, but +1 for b now.
only use "Java-like" syntax if "goto" will never be implemented
Re: [PHP-DEV] GOTO and/or BREAK LABEL
Please, Xuefer! Your vote was already recorded, shhh!
- Original Message -
From: "Xuefer" <[EMAIL PROTECTED]>
To: "Ford, Mike" <[EMAIL PROTECTED]>
Cc: "Dmitry Stogov" <[EMAIL PROTECTED]>;
Sent: Thursday, March 09, 2006 5:19 AM
Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL
If the "Java-like" syntax is seen as confusing, what about, as in some
other languages, interpolating the label into the for/foreach/while
statement:
for () label {...} or for label (...) {...}
a. label: for () { break label; } AND label: { for () {
break label; } } (see
http://www.rgagnon.com/javadetails/java-0500.html )
b. for () label { break label; }
c. for () { break label; } label:
ok, i was +1 for c, but +1 for b now.
only use "Java-like" syntax if "goto" will never be implemented
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? It may make sense, because it is not a full analog of C's goto statement. It is a limited "goto". It allows jump back and forward, but not INTO loops and switch statements. Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL
On 3/9/06, Steph Fox <[EMAIL PROTECTED]> wrote: > Please, Xuefer! Your vote was already recorded, shhh! i wasn't to vote more than once. it's same vote but with a bit different syntax changed. oh well, the result is out, this is only my explaination.
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
On Thu, 9 Mar 2006, Dmitry Stogov wrote: > Hi, > > The solution (2) - "goto only" is the winner. > So in case of no serious objections, I'll commit the "goto.diff" patch in 24 > hour. > > The last question: > What do you thin about Andi's solution about using "jump" instead of "goto"? I don't really mind... but I wonder why you want to do this? Both work equally well and most people are familiar with the term "goto". Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
I am indifferent - "goto" or "jump", but may be others don't. Thanks. Dmitry. > -Original Message- > From: Derick Rethans [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 09, 2006 11:09 AM > To: Dmitry Stogov > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) > > > On Thu, 9 Mar 2006, Dmitry Stogov wrote: > > > Hi, > > > > The solution (2) - "goto only" is the winner. > > So in case of no serious objections, I'll commit the > "goto.diff" patch > > in 24 hour. > > > > The last question: > > What do you thin about Andi's solution about using "jump" > instead of > > "goto"? > > I don't really mind... but I wonder why you want to do this? > Both work > equally well and most people are familiar with the term "goto". > > Derick > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hi, Dmitry Stogov wrote: I am indifferent - "goto" or "jump", but may be others don't. what about `escape`? Thanks. Dmitry. -Original Message- From: Derick Rethans [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 11:09 AM To: Dmitry Stogov Cc: internals@lists.php.net Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) On Thu, 9 Mar 2006, Dmitry Stogov wrote: Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? I don't really mind... but I wonder why you want to do this? Both work equally well and most people are familiar with the term "goto". Derick -- Andrey -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hi, sorry for sending second email. Another choice could be `leave`, which seems better than `escape` (clashes with escaping sequences). Andrey Andrey Hristov wrote: Hi, Dmitry Stogov wrote: I am indifferent - "goto" or "jump", but may be others don't. what about `escape`? Thanks. Dmitry. -Original Message- From: Derick Rethans [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 11:09 AM To: Dmitry Stogov Cc: internals@lists.php.net Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) On Thu, 9 Mar 2006, Dmitry Stogov wrote: Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? I don't really mind... but I wonder why you want to do this? Both work equally well and most people are familiar with the term "goto". Derick -- Andrey -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
At 1141902889, Andrey Hristov wrote: > sorry for sending second email. Another choice could be `leave`, which > seems better than `escape` (clashes with escaping sequences). I think `leave` has too many connotations with `break` and similar commands, and could be misleading. -- Jon Dowland http://alcopop.org/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
At 1141895342, Derick Rethans wrote: > On Thu, 9 Mar 2006, Dmitry Stogov wrote: > > The last question: What do you thin about Andi's solution about > > using "jump" instead of "goto"? > > I don't really mind... but I wonder why you want to do this? Both work > equally well and most people are familiar with the term "goto". Seeing as this does not behave the same as the classic C "goto", re-using the term could prove to be misleading and confusing. For this reason I prefer "jump". -- Jon Dowland http://alcopop.org/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Jon Dowland wrote: At 1141902889, Andrey Hristov wrote: sorry for sending second email. Another choice could be `leave`, which seems better than `escape` (clashes with escaping sequences). I think `leave` has too many connotations with `break` and similar commands, and could be misleading. I don't concur and there is documentation for the language. To get to a language one needs to read a bit of its documentation. In every language I know break leaves the current loop, in PHP it's overloaded that the PC could be set after `n` loops. Andrey -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
jump makes more sense than goto. We bounced it off in the Paris meeting, IIRC it was fairly popular in case we go down the route of this semantics. Zeev At 10:03 09/03/2006, Dmitry Stogov wrote: Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? It may make sense, because it is not a full analog of C's goto statement. It is a limited "goto". It allows jump back and forward, but not INTO loops and switch statements. Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
At 10:03 09/03/2006, Dmitry Stogov wrote: >>The last question: >>What do you thin about Andi's solution about using "jump" instead of "goto"? Great! Yet another keyword. PHP keeps surprising the world... >>It may make sense, because it is not a full analog of C's goto statement. It >>is a limited "goto". It allows jump back and forward, but not INTO loops and >>switch statements. The "break number" syntax will still be available? Otherwise from your words I understand that there is no way of breaking/jumping a lot of nested cycles and still be in a cycle. I wish I could vote for a better version of Java labeled breaks :( João C Morais Zeev Suraski wrote: jump makes more sense than goto. We bounced it off in the Paris meeting, IIRC it was fairly popular in case we go down the route of this semantics. Zeev At 10:03 09/03/2006, Dmitry Stogov wrote: Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? It may make sense, because it is not a full analog of C's goto statement. It is a limited "goto". It allows jump back and forward, but not INTO loops and switch statements. Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
My vote is +1 for goto, just because that largely describes what it does and how it is used. I don't mind if it winds up being called jump, I just think it will be easier for people to find it when they need it if it is called 'goto'. 'goto' also comes with all the usual anti-goto propaganda that will help discourage people that shouldn't be using it from using it. --Wez. On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: > Hi, > > The solution (2) - "goto only" is the winner. > So in case of no serious objections, I'll commit the "goto.diff" patch in 24 > hour. > > The last question: > What do you thin about Andi's solution about using "jump" instead of "goto"? > > It may make sense, because it is not a full analog of C's goto statement. It > is a limited "goto". It allows jump back and forward, but not INTO loops and > switch statements. > > Thanks. Dmitry. > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
+1 for goto -1 for jump Wez Furlong wrote: My vote is +1 for goto, just because that largely describes what it does and how it is used. I don't mind if it winds up being called jump, I just think it will be easier for people to find it when they need it if it is called 'goto'. 'goto' also comes with all the usual anti-goto propaganda that will help discourage people that shouldn't be using it from using it. --Wez. On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: Hi, The solution (2) - "goto only" is the winner. So in case of no serious objections, I'll commit the "goto.diff" patch in 24 hour. The last question: What do you thin about Andi's solution about using "jump" instead of "goto"? It may make sense, because it is not a full analog of C's goto statement. It is a limited "goto". It allows jump back and forward, but not INTO loops and switch statements. Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hello Wez, just to continue on this nice argument: Jump reminds me of the worst addition to c ever: longjump. marcus Friday, March 10, 2006, 2:36:56 PM, you wrote: > My vote is +1 for goto, just because that largely describes what it > does and how it is used. I don't mind if it winds up being called > jump, I just think it will be easier for people to find it when they > need it if it is called 'goto'. 'goto' also comes with all the usual > anti-goto propaganda that will help discourage people that shouldn't > be using it from using it. > --Wez. > On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: >> Hi, >> >> The solution (2) - "goto only" is the winner. >> So in case of no serious objections, I'll commit the "goto.diff" patch in 24 >> hour. >> >> The last question: >> What do you thin about Andi's solution about using "jump" instead of "goto"? >> >> It may make sense, because it is not a full analog of C's goto statement. It >> is a limited "goto". It allows jump back and forward, but not INTO loops and >> switch statements. >> >> Thanks. Dmitry. >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
We already have exceptions, so we don't need another longjump :) "jump" or "goto"? Just make common decision and I will change it. Thanks. Dmitry. > -Original Message- > From: Marcus Boerger [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 11, 2006 1:22 AM > To: Wez Furlong > Cc: Dmitry Stogov; internals@lists.php.net > Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) > > > Hello Wez, > >just to continue on this nice argument: Jump reminds me of > the worst addition to c ever: longjump. > > marcus > > Friday, March 10, 2006, 2:36:56 PM, you wrote: > > > My vote is +1 for goto, just because that largely describes what it > > does and how it is used. I don't mind if it winds up being called > > jump, I just think it will be easier for people to find it > when they > > need it if it is called 'goto'. 'goto' also comes with all > the usual > > anti-goto propaganda that will help discourage people that > shouldn't > > be using it from using it. > > > --Wez. > > > On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: > >> Hi, > >> > >> The solution (2) - "goto only" is the winner. > >> So in case of no serious objections, I'll commit the "goto.diff" > >> patch in 24 hour. > >> > >> The last question: > >> What do you thin about Andi's solution about using "jump" > instead of > >> "goto"? > >> > >> It may make sense, because it is not a full analog of C's goto > >> statement. It is a limited "goto". It allows jump back and > forward, > >> but not INTO loops and switch statements. > >> > >> Thanks. Dmitry. > >> > >> -- > >> PHP Internals - PHP Runtime Development Mailing List > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > > > > Best regards, > Marcus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hello Dmitry, my advice just like Wez' is to name it 'goto' because that is what it is. (to drop the 2nd part that might have confused you). best regards marcus p.s.: To make me happy you'd have to drop the mess Sunday, March 12, 2006, 10:44:19 AM, you wrote: > We already have exceptions, so we don't need another longjump :) > "jump" or "goto"? Just make common decision and I will change it. > Thanks. Dmitry. >> -Original Message- >> From: Marcus Boerger [mailto:[EMAIL PROTECTED] >> Sent: Saturday, March 11, 2006 1:22 AM >> To: Wez Furlong >> Cc: Dmitry Stogov; internals@lists.php.net >> Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) >> >> >> Hello Wez, >> >>just to continue on this nice argument: Jump reminds me of >> the worst addition to c ever: longjump. >> >> marcus >> >> Friday, March 10, 2006, 2:36:56 PM, you wrote: >> >> > My vote is +1 for goto, just because that largely describes what it >> > does and how it is used. I don't mind if it winds up being called >> > jump, I just think it will be easier for people to find it >> when they >> > need it if it is called 'goto'. 'goto' also comes with all >> the usual >> > anti-goto propaganda that will help discourage people that >> shouldn't >> > be using it from using it. >> >> > --Wez. >> >> > On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> >> >> The solution (2) - "goto only" is the winner. >> >> So in case of no serious objections, I'll commit the "goto.diff" >> >> patch in 24 hour. >> >> >> >> The last question: >> >> What do you thin about Andi's solution about using "jump" >> instead of >> >> "goto"? >> >> >> >> It may make sense, because it is not a full analog of C's goto >> >> statement. It is a limited "goto". It allows jump back and >> forward, >> >> but not INTO loops and switch statements. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Dmitry Stogov wrote: We already have exceptions, so we don't need another longjump :) "jump" or "goto"? Just make common decision and I will change it. Dmitry, maybe I have overlooked a single post, but I have yet to see a single post favoring "jump" over "goto". The common decision is here and it is "goto". regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Dmitry, maybe I have overlooked a single post, but I have yet to see a single post favoring "jump" over "goto". The common decision is here and it is "goto". Lukas, that's extremely odd. Check history! (when most of the core team agreed on jump originally, for a start). I've seen five very vocal pro 'goto's here and NO good reasons given for it. There are several good reasons against. - Steph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
On 3/12/06, Steph Fox <[EMAIL PROTECTED]> wrote: > Lukas, that's extremely odd. Check history! (when most of the core team > agreed on jump originally, for a start). I've seen five very vocal pro > 'goto's here and NO good reasons given for it. There are several good > reasons against. The result of the vote in this thread is clear. No matter what your history says, I think it is time to commit it and move to more interesting topic. --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
I'm fine with goto too. At 02:40 AM 3/12/2006, Marcus Boerger wrote: Hello Dmitry, my advice just like Wez' is to name it 'goto' because that is what it is. (to drop the 2nd part that might have confused you). best regards marcus p.s.: To make me happy you'd have to drop the mess Sunday, March 12, 2006, 10:44:19 AM, you wrote: > We already have exceptions, so we don't need another longjump :) > "jump" or "goto"? Just make common decision and I will change it. > Thanks. Dmitry. >> -Original Message- >> From: Marcus Boerger [mailto:[EMAIL PROTECTED] >> Sent: Saturday, March 11, 2006 1:22 AM >> To: Wez Furlong >> Cc: Dmitry Stogov; internals@lists.php.net >> Subject: Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion) >> >> >> Hello Wez, >> >>just to continue on this nice argument: Jump reminds me of >> the worst addition to c ever: longjump. >> >> marcus >> >> Friday, March 10, 2006, 2:36:56 PM, you wrote: >> >> > My vote is +1 for goto, just because that largely describes what it >> > does and how it is used. I don't mind if it winds up being called >> > jump, I just think it will be easier for people to find it >> when they >> > need it if it is called 'goto'. 'goto' also comes with all >> the usual >> > anti-goto propaganda that will help discourage people that >> shouldn't >> > be using it from using it. >> >> > --Wez. >> >> > On 3/9/06, Dmitry Stogov <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> >> >> The solution (2) - "goto only" is the winner. >> >> So in case of no serious objections, I'll commit the "goto.diff" >> >> patch in 24 hour. >> >> >> >> The last question: >> >> What do you thin about Andi's solution about using "jump" >> instead of >> >> "goto"? >> >> >> >> It may make sense, because it is not a full analog of C's goto >> >> statement. It is a limited "goto". It allows jump back and >> forward, >> >> but not INTO loops and switch statements. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Lukas, that's extremely odd. Check history! (when most of the core team agreed on jump originally, for a start). I've seen five very vocal pro 'goto's here and NO good reasons given for it. There are several good reasons against. The result of the vote in this thread is clear. No matter what your history says, I think it is time to commit it and move to more interesting topic. I think I'm tired of being attacked. This is not 'my history'. Ilia, Zeev, Dmitry, and a bunch of other people wanted it to be called 'jump'. If you choose to ignore them because you don't like it, fine, but there's no reason to be nasty with it. It'd be better to give a sensible reason for calling it 'goto' if that's what you want - as far as I can see there aren't any. - Steph -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Can't you g(irl|uy)s install somewhere a right pool so people can simply vote ? With some identification, so you can sort out common people, registered, core, etc... results ? I mean for simple choices e.g. goto|jump|both, otherwise, as was recently proposed, RFC are certainly nice and more efficient when more technical to consider. And not saying discussions here are not interesting. -- toggg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Let's just call it goto and be done with it. It seems that for the people who will use this feature "goto" name will cause the least amount of "WTF". Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Hello bertrand, just to clearify this, we don't do voting here becuase it is impossible to bring a majority of php users here or decide who is important and so on. Thus we are only doing surveys here even if called voting. And i assume that all people on this list have better things to do than implementing a survey system for undiscussed php features. Instead we stay with our habits and continue to openly discuss things until some of the developers who feel responsible have made their mind and found a consensus. That served us all best in the past. Even if it means that we did not get all the features we wanted or did not get them in the form we wanted. And even if it means that we have to discuss stuff on long threads which includes people who actually have no meaning on a request, just want to say something or even have no idea what is going on soever. The advantage still is that often enough we get good feedback and learn from each other by those discussions. best regards marcus Sunday, March 12, 2006, 8:00:11 PM, you wrote: > Can't you g(irl|uy)s install somewhere a right pool so people can simply > vote ? > With some identification, so you can sort out common people, registered, > core, etc... results ? > I mean for simple choices e.g. goto|jump|both, > otherwise, as was recently proposed, RFC are certainly nice and more > efficient when more technical to consider. > And not saying discussions here are not interesting. > -- > toggg Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
RE: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Seems the majority prefers "goto". I'll change "jump" to "goto" tomorrow in case of no serious objections. Thanks. Dmitry. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] GOTO and/or BREAK LABEL (conclusion)
Like case-sensitivity. -Andrei P.S. Joking, I am _just_ JOKING! Have a sense of humor, people. On Mar 12, 2006, at 8:50 AM, Pierre wrote: On 3/12/06, Steph Fox <[EMAIL PROTECTED]> wrote: Lukas, that's extremely odd. Check history! (when most of the core team agreed on jump originally, for a start). I've seen five very vocal pro 'goto's here and NO good reasons given for it. There are several good reasons against. The result of the vote in this thread is clear. No matter what your history says, I think it is time to commit it and move to more interesting topic. --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
