CSBwin/User Questions - Revision history

WikiSysop at 16:27, 6 January 2009

2009-01-06T16:27:43Z

← Older revision		Revision as of 16:27, 6 January 2009
Line 98:		Line 98:
	ANSWER: Yes. 'Jumps' and 'GoSubs' do not alter the value of 'nextState'. Only the very first instruction executed when the DSA is activated by a message and &SETNEWSTATE can change 'nextState'.		ANSWER: Yes. 'Jumps' and 'GoSubs' do not alter the value of 'nextState'. Only the very first instruction executed when the DSA is activated by a message and &SETNEWSTATE can change 'nextState'.

	[[Category:~~CSBWin~~\|User Questions]]		[[Category:CSBwin\|User Questions]]

WikiSysop: added category

2009-01-06T16:24:30Z

added category

← Older revision		Revision as of 16:24, 6 January 2009
Line 97:		Line 97:

	ANSWER: Yes. 'Jumps' and 'GoSubs' do not alter the value of 'nextState'. Only the very first instruction executed when the DSA is activated by a message and &SETNEWSTATE can change 'nextState'.		ANSWER: Yes. 'Jumps' and 'GoSubs' do not alter the value of 'nextState'. Only the very first instruction executed when the DSA is activated by a message and &SETNEWSTATE can change 'nextState'.

			[[Category:CSBWin\|User Questions]]

Paul Stevens: /* Flow Control and nextState */

2008-11-04T16:41:50Z

Flow Control and nextState

← Older revision		Revision as of 16:41, 4 November 2008
Line 95:		Line 95:
	=== Flow Control and ''nextState'' ===		=== Flow Control and ''nextState'' ===
	The ''nextState'' modifier of an instruction is ignore for all instructions other than the first in the sequence. How does this work with the various Flow-Control instructions, say '''&J*'''. Does the DSA keep the same state it was in (assuming no '''&SETNEWSTATE''' instructions in the called routine)?		The ''nextState'' modifier of an instruction is ignore for all instructions other than the first in the sequence. How does this work with the various Flow-Control instructions, say '''&J*'''. Does the DSA keep the same state it was in (assuming no '''&SETNEWSTATE''' instructions in the called routine)?

			ANSWER: Yes. 'Jumps' and 'GoSubs' do not alter the value of 'nextState'. Only the very first instruction executed when the DSA is activated by a message and &SETNEWSTATE can change 'nextState'.

Paul Stevens: /* Case - syntax */

2008-11-04T15:20:17Z

Case - syntax

← Older revision		Revision as of 15:20, 4 November 2008
Line 62:		Line 62:

	ANSWER: ??{<case><case><case>........} (n ... )		ANSWER: ??{<case><case><case>........} (n ... )

			The "(n ... )" part of the syntax definition says that the '??' statement needs a single number ('n') on the top of the stack and replaces it with nothing.

	A 'case' statement is normally used when a variable can have many values and you want something different to happen for each of those values. Let us make a particular example. Let us say that the parameter B can have three different values: 4, 12, and 7. If the value is 4 we want to jump to 6S2; if the value is 7 we want to jump to 3T1; if the value is 12 we want to jump to 3T2. If parameter B is any other value then we want to place the number 105 on the stack. Here is the code (notice that the outermost delimiters are braces, not parentheses):		A 'case' statement is normally used when a variable can have many values and you want something different to happen for each of those values. Let us make a particular example. Let us say that the parameter B can have three different values: 4, 12, and 7. If the value is 4 we want to jump to 6S2; if the value is 7 we want to jump to 3T1; if the value is 12 we want to jump to 3T2. If parameter B is any other value then we want to place the number 105 on the stack. Here is the code (notice that the outermost delimiters are braces, not parentheses):

Paul Stevens: /* Case - syntax */

2008-11-04T15:16:26Z

Case - syntax

← Older revision		Revision as of 15:16, 4 November 2008
Line 60:		Line 60:
	=== Case - syntax ===		=== Case - syntax ===
	I'm not understanding the syntax, could someone please provide some examples?		I'm not understanding the syntax, could someone please provide some examples?

			ANSWER: ??{<case><case><case>........} (n ... )

			A 'case' statement is normally used when a variable can have many values and you want something different to happen for each of those values. Let us make a particular example. Let us say that the parameter B can have three different values: 4, 12, and 7. If the value is 4 we want to jump to 6S2; if the value is 7 we want to jump to 3T1; if the value is 12 we want to jump to 3T2. If parameter B is any other value then we want to place the number 105 on the stack. Here is the code (notice that the outermost delimiters are braces, not parentheses):

			LB ??{(4,6S2)(7,3T1)(12,3T2)} L105

	=== IfElse - syntax ===		=== IfElse - syntax ===

Paul Stevens: /* What are parameters: C,D,etc? */

2008-11-04T14:47:32Z

What are parameters: C,D,etc?

← Older revision		Revision as of 14:47, 4 November 2008
Line 19:		Line 19:
	=== Parameters ===		=== Parameters ===
	==== What are parameters: C,D,etc? ====		==== What are parameters: C,D,etc? ====

			ANSWER: In a given cell of the dungeon you may place several DSAs. They are piled up just as several daggers might be piled up in a corner somewhere. Each DSA has two parameters named 'A' and 'B'. But each DSA can also reference the parameters of all the DSAs that are BELOW it in the pile of DSAs (or list of DSAs). The DSA directly below is referenced by specifying paramteter C and D. The DSA below that is referenced by parameter E nd F. Notice that you cannot reference the parameters of DSAs that are ABOVE, only the ones BELOW. Normally, those DSAs that are referenced as C, D, etc. are 'Do Nothing' and have no code. They are placed in the dungeon only to provide additional parameters for a DSA above them in the pile. But that is not a restriction. When a message is sent to a cell in the dungeon, each DSA in that cell will be activated in turn and any code will be executed. Assume that two DSAs are in the pile. The top DSA can reference parameters A, B, C, and D. The bottom DSA can only reference its own two parameters as A and B.

	=== Stack ===		=== Stack ===

Paul Stevens: /* IfElse - syntax */

2008-10-31T03:40:11Z

IfElse - syntax

← Older revision		Revision as of 03:40, 31 October 2008
Line 65:		Line 65:

	?X means do X if TOS is non-zero.		?X means do X if TOS is non-zero.

	?X:Y means do X if TOS is non-zero else do Y.		?X:Y means do X if TOS is non-zero else do Y.

	?:Y means do Y if TOS is zero.		?:Y means do Y if TOS is zero.

	TOS is the value on the top of the stack.		TOS is the value on the top of the stack.

	X and Y can only be 'J'umps or 'G'otos.		X and Y can only be 'J'umps or 'G'otos.

Paul Stevens: /* IfElse - syntax */

2008-10-31T03:39:44Z

IfElse - syntax

@@ Line 61: / Line 61: @@
 === IfElse - syntax  ===
 I'm not understanding the syntax, could someone please provide some examples?
 === Flow Control and ''nextState'' ===
 The ''nextState'' modifier of an instruction is ignore for all instructions other than the first in the sequence.  How does this work with the various Flow-Control instructions, say '''&J*'''. Does the DSA keep the same state it was in (assuming no '''&SETNEWSTATE''' instructions in the called routine)?

Paul Stevens: /* L$ */

2008-10-31T03:30:05Z

← Older revision		Revision as of 03:30, 31 October 2008
Line 54:		Line 54:
	This is stated to push the location of the current ''master cell''. What is it?		This is stated to push the location of the current ''master cell''. What is it?

	ANSWER: The Master/Slave concept has never been fully implemented and there is no need to implement it. So the location of the 'Master cell' is simply the location within the dungeon where you put an instance of the DSA. If it were a 'Pit' then it would be the location of the pit. If the word 'Master' had not been included in the description then there would probably be no confusion.		ANSWER: The Master/Slave concept has never been fully implemented and there is no need to implement it. So the location of the 'Master cell' is simply the location within the dungeon where you put an instance of the DSA. If it were a 'Pit' then it would be the location of the pit. But it is a DSA so it is the location of the DSA. If the word 'Master' had not been included in the description then there would probably be no confusion.

	=== Case - syntax ===		=== Case - syntax ===

Paul Stevens: /* L$ */

2008-10-31T03:29:16Z

← Older revision		Revision as of 03:29, 31 October 2008
Line 53:		Line 53:
	=== L$ ===		=== L$ ===
	This is stated to push the location of the current ''master cell''. What is it?		This is stated to push the location of the current ''master cell''. What is it?

			ANSWER: The Master/Slave concept has never been fully implemented and there is no need to implement it. So the location of the 'Master cell' is simply the location within the dungeon where you put an instance of the DSA. If it were a 'Pit' then it would be the location of the pit. If the word 'Master' had not been included in the description then there would probably be no confusion.

	=== Case - syntax ===		=== Case - syntax ===