Talk:Control Structures - Revision history

Yoyo: question about static

2019-03-26T22:02:43Z

question about static

← Older revision		Revision as of 22:02, 26 March 2019
Line 54:		Line 54:

	:The loop ends when the expression is false. --[[User:Bale\|Bale]] 04:32, 23 June 2010 (UTC)		:The loop ends when the expression is false. --[[User:Bale\|Bale]] 04:32, 23 June 2010 (UTC)

			== static ==

			When using static in a function to declare/initialize variables do the variables retain those values from call to call, or will this cause an error when trying to run? Thanks --[[User:Yoyo\|Yoyo]] ([[User talk:Yoyo\|talk]]) 22:02, 26 March 2019 (UTC)

Bale: add attribution

2010-06-23T04:37:02Z

add attribution

← Older revision		Revision as of 04:37, 23 June 2010
Line 44:		Line 44:

	Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)		Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)
	* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).		* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys). -- [[User:Jasonharper]] 16:26, 22 June 2010 (UTC) (signature added later)

	::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:08, 23 June 2010 (UTC)		::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:08, 23 June 2010 (UTC)

Bale: /* repeat until */

2010-06-23T04:32:50Z

repeat until

← Older revision		Revision as of 04:32, 23 June 2010
Line 51:		Line 51:

	Does it loop as long as the boolean expression is true, or false? I assume false, somewhat different from how [http://en.wikipedia.org/wiki/Do_while_loop do while loop]s work. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:19, 23 June 2010 (UTC)		Does it loop as long as the boolean expression is true, or false? I assume false, somewhat different from how [http://en.wikipedia.org/wiki/Do_while_loop do while loop]s work. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:19, 23 June 2010 (UTC)

			:The loop ends when the expression is false. --[[User:Bale\|Bale]] 04:32, 23 June 2010 (UTC)

PhilmASTErpLus: How do "repeat...until" loops work?

2010-06-23T04:19:20Z

How do "repeat...until" loops work?

← Older revision		Revision as of 04:19, 23 June 2010
Line 46:		Line 46:
	* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).		* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).
	::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:08, 23 June 2010 (UTC)		::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:08, 23 June 2010 (UTC)


			== repeat until ==

			Does it loop as long as the boolean expression is true, or false? I assume false, somewhat different from how [http://en.wikipedia.org/wiki/Do_while_loop do while loop]s work. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:19, 23 June 2010 (UTC)

PhilmASTErpLus: Request for a full-length reference on maps and aggregates

2010-06-23T04:08:43Z

Request for a full-length reference on maps and aggregates

← Older revision		Revision as of 04:08, 23 June 2010
Line 45:		Line 45:
	Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)		Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)
	* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).		* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).
	::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future.		::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future. --[[User:PhilmASTErpLus\|PhilmASTErpLus]] 04:08, 23 June 2010 (UTC)

PhilmASTErpLus: Request for a full-length reference on maps and aggregates

2010-06-23T04:08:35Z

Request for a full-length reference on maps and aggregates

← Older revision		Revision as of 04:08, 23 June 2010
Line 45:		Line 45:
	Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)		Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)
	* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).		* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).
			::I know, but I felt it would take too much pain to write a full-length guide on maps and aggregates that includes that information. Hopefully, someone would in the future.

Jasonharper at 16:26, 22 June 2010

2010-06-22T16:26:22Z

← Older revision		Revision as of 16:26, 22 June 2010
Line 44:		Line 44:

	Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)		Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)
			* foreach DOES NOT SORT - it uses whatever ordering is provided by the aggregate you're iterating over. For maps and arrays, the objects themselves maintain the keys in sorted order. For plural typed constants, the ordering is however the elements were originally listed, which is completely arbitrary (and can even include duplicate keys).

Heeheehee: Re: foreach's auto-sort

2010-06-22T12:10:53Z

Re: foreach's auto-sort

← Older revision		Revision as of 12:10, 22 June 2010
Line 42:		Line 42:

	That looks good; I'd add in one line with a different variable though, just to make the differentiation in use clear. Such as an initial check for y > 9000 or something. Then again, I pretty much figured it out from what's on the page, so I'm not sure it's necessary. Perhaps three samples are in order: a simple switch with a generic variable to test, your example, and a "This won't work" example that tries to mix the two. --[[User:StDoodle\|StDoodle (#1059825)]] 13:51, 4 May 2010 (UTC)		That looks good; I'd add in one line with a different variable though, just to make the differentiation in use clear. Such as an initial check for y > 9000 or something. Then again, I pretty much figured it out from what's on the page, so I'm not sure it's necessary. Perhaps three samples are in order: a simple switch with a generic variable to test, your example, and a "This won't work" example that tries to mix the two. --[[User:StDoodle\|StDoodle (#1059825)]] 13:51, 4 May 2010 (UTC)

			Regarding foreach and sorting: since it sorts by index, not by value, that should be mentioned somewhere in that blurb. --[[User:Heeheehee\|Heeheehee]] 12:10, 22 June 2010 (UTC)

StDoodle at 13:51, 4 May 2010

2010-05-04T13:51:45Z

← Older revision		Revision as of 13:51, 4 May 2010
Line 40:		Line 40:
	</syntaxhighlight>}}		</syntaxhighlight>}}
	Do you think an example like that would be helpful? --[[User:Bale\|Bale]] 03:19, 4 May 2010 (UTC)		Do you think an example like that would be helpful? --[[User:Bale\|Bale]] 03:19, 4 May 2010 (UTC)

			That looks good; I'd add in one line with a different variable though, just to make the differentiation in use clear. Such as an initial check for y > 9000 or something. Then again, I pretty much figured it out from what's on the page, so I'm not sure it's necessary. Perhaps three samples are in order: a simple switch with a generic variable to test, your example, and a "This won't work" example that tries to mix the two. --[[User:StDoodle\|StDoodle (#1059825)]] 13:51, 4 May 2010 (UTC)

Bale at 03:19, 4 May 2010

2010-05-04T03:19:01Z

← Older revision		Revision as of 03:19, 4 May 2010
Line 12:		Line 12:

	Er, that is to say, I knew how to use them with a top-level variable, but not that you could omit that and use a sep. expression each time... and I could swear I tried to use expressions that way (apparently you can't do both at once!). :P --[[User:StDoodle\|StDoodle (#1059825)]] 02:29, 4 May 2010 (UTC)		Er, that is to say, I knew how to use them with a top-level variable, but not that you could omit that and use a sep. expression each time... and I could swear I tried to use expressions that way (apparently you can't do both at once!). :P --[[User:StDoodle\|StDoodle (#1059825)]] 02:29, 4 May 2010 (UTC)

			I'm wondering if a more explicit example is necessary. What I'm talking about is:

			{{
			CodeSample\|
			code=
			<syntaxhighlight>
			switch {
			case x < 0 && x == x % 2:
			print(x+" is negative and even");
			break;
			case x < 0:
			print(x+" is negative and odd");
			break;
			case x == 0:
			print("x is zero");
			break;
			case x == x % 2 && x < 10:
			print(x+" is a positive one digit even number");
			break;
			case x != x % 2
			print(x+" is an odd number");
			break;
			default:
			print(x+" is greater than 9");
			}
			</syntaxhighlight>}}
			Do you think an example like that would be helpful? --[[User:Bale\|Bale]] 03:19, 4 May 2010 (UTC)