Binding Strength - Revision history

WikiSysop: /* Vector Notation */

2019-09-10T11:17:38Z

Vector Notation

← Older revision		Revision as of 07:17, 10 September 2019
Line 49:		Line 49:
	In particular,		In particular,

	* A dyadic operator written as    <~~aplcl~~>… dop 1 2 3 4</~~aplcl~~>    is interpreted as having a right operand ('''short''' right scope) of <~~aplcl~~>1</~~aplcl~~> and a right argument ('''long''' right scope) of <~~aplcl~~>2 3 4</~~aplcl~~>.		* A dyadic operator written as    <apll>… dop 1 2 3 4</apll>    is interpreted as having a right operand ('''short''' right scope) of <apll>1</apll> and a right argument ('''long''' right scope) of <apll>2 3 4</apll>.
	* A hyperator written as either    <~~aplcl~~>1 2 3 4 mhmo</~~aplcl~~>    or    <~~aplcl~~>1 2 3 4 mhdo …</~~aplcl~~>    is interpreted as having a left hyperand ('''short''' left scope) of <~~aplcl~~>4</~~aplcl~~> and a left operand ('''long''' left scope) of <~~aplcl~~>1 2 3</~~aplcl~~>.		* A hyperator written as either    <apll>1 2 3 4 mhmo</apll>    or    <apll>1 2 3 4 mhdo …</apll>    is interpreted as having a left hyperand ('''short''' left scope) of <apll>4</apll> and a left operand ('''long''' left scope) of <apll>1 2 3</apll>.
	* A dyadic hyperator written as    <~~aplcl~~>… dhmo 1 2 3 4</~~aplcl~~>    is interpreted as having a right hyperand ('''short''' right scope) of <~~aplcl~~>1</~~aplcl~~> and a right argument ('''long''' right scope) of <~~aplcl~~>2 3 4</~~aplcl~~>.		* A dyadic hyperator written as    <apll>… dhmo 1 2 3 4</apll>    is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll> and a right argument ('''long''' right scope) of <apll>2 3 4</apll>.
	* A dyadic hyperator written as    <~~aplcl~~>… dhdo 1 2 3 4</~~aplcl~~>    is interpreted as having a right hyperand ('''short''' right scope) of <~~aplcl~~>1</~~aplcl~~>, a right operand ('''short''' right scope) of <~~aplcl~~>2</~~aplcl~~>, and a right argument ('''long''' right scope) of <~~aplcl~~>3 4</~~aplcl~~>.		* A dyadic hyperator written as    <apll>… dhdo 1 2 3 4</apll>    is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll>, a right operand ('''short''' right scope) of <apll>2</apll>, and a right argument ('''long''' right scope) of <apll>3 4</apll>.

	To reduce confusion, use parentheses such as <~~aplcl~~>(LO (LH dhdo 1) 2) 3 4</~~aplcl~~>.		To reduce confusion, use parentheses such as <apll>(LO (LH dhdo 1) 2) 3 4</apll>.

	Abbreviations:		Abbreviations:

WikiSysop at 09:38, 8 May 2019

2019-05-08T09:38:28Z

← Older revision		Revision as of 05:38, 8 May 2019
Line 62:		Line 62:
	* <apll>dhmo</apll> Dyadic Hyperand Monadic Operand ...		* <apll>dhmo</apll> Dyadic Hyperand Monadic Operand ...
	* <apll>dhdo</apll> Dyadic Hyperand Dyadic Operand ...		* <apll>dhdo</apll> Dyadic Hyperand Dyadic Operand ...

			Also, see [[Hyperators#Syntax_Glitch\|Syntax Glitch]].

	==References==		==References==

	<references />		<references />

WikiSysop at 09:22, 24 March 2019

2019-03-24T09:22:26Z

← Older revision		Revision as of 05:22, 24 March 2019
Line 1:		Line 1:
	==Table==		==Table==

	The rules for how Variables, Functions, Operators, Hyperators and other syntactic elements combine are covered in the following table:		The rules for how Variables, Functions, Operators, Hyperators and other syntactic elements combine are covered in the following table which is an extension of the one used in APL2<ref name="APL2BindingStrength">[https://www.ibm.com/downloads/cas/ZOKMYKOY APL2 Reference Manual, Second Edition, 1994, SH21-1061-01, pp. 33-36]</ref>:


	{\| border="1" cellspacing="0" cellpadding="5"		{\| border="1" cellspacing="0" cellpadding="5"
Line 40:		Line 41:
	\|}		\|}

	One way to look at these rules is ~~that if you are given~~ three names ~~and/~~or symbols, ~~you can always tell whether~~ the ~~middle object binds to~~ the left or right ~~object~~.		One way to look at these rules is described in the APL2 Reference Manual as "Binding defines how names and symbols group for evaluation. Given three names (or symbols), binding strength determines if the center one is associated with the name (or symbol) on the left or the right."<ref name="APL2BindingStrength" />

	==Vector Notation==		==Vector Notation==
Line 61:		Line 62:
	* <apll>dhmo</apll> Dyadic Hyperand Monadic Operand ...		* <apll>dhmo</apll> Dyadic Hyperand Monadic Operand ...
	* <apll>dhdo</apll> Dyadic Hyperand Dyadic Operand ...		* <apll>dhdo</apll> Dyadic Hyperand Dyadic Operand ...

			==References==

			<references />

WikiSysop: /* Vector Notation */

2019-03-22T15:56:27Z

Vector Notation

← Older revision		Revision as of 11:56, 22 March 2019
Line 44:		Line 44:
	==Vector Notation==		==Vector Notation==

	As the above table indicates, Vector Notation has a lower Binding Strength than both a right operand to its operator and either hyperand to its hyperator. One consequence of this is a change introduced in NARS2000 Version 0.5.10 w.r.t. Numeric Strands. ~~In particular~~,		As the above table indicates, Vector Notation has a lower Binding Strength than both a right operand to its operator and either hyperand to its hyperator. One consequence of this is a change introduced in NARS2000 Version 0.5.10 w.r.t. Numeric Strands, in conjunction with the '''short scope''' of the three elements: Right Operands, Left Hyperands, and Right Hyperands.

	* A dyadic operator written as <apll>… dop 1 2 3</apll> is interpreted as having a right operand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.		In particular,
	* A hyperator written as either <apll>1 2 3 mhmo</apll> or <apll>1 2 3 mhdo …</apll> is interpreted as having a left hyperand ('''short''' left scope) of <apll>3</apll> and a left operand ('''long''' left scope) of <apll>1 2</apll>.
	* A dyadic hyperator written as <apll>… dhmo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.
	* A dyadic hyperator written as <apll>… dhdo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll>, ~~a right operand ('''short''' right scope) of <apll>2</apll>, and a right argument of <apll>3</apll>.~~

	To reduce confusion, use parentheses such as <~~apll~~>(LO (LH dhdo 1) 2) 3</~~apll~~>.		* A dyadic operator written as    <aplcl>… dop 1 2 3 4</aplcl>    is interpreted as having a right operand ('''short''' right scope) of <aplcl>1</aplcl> and a right argument ('''long''' right scope) of <aplcl>2 3 4</aplcl>.
			* A hyperator written as either    <aplcl>1 2 3 4 mhmo</aplcl>    or    <aplcl>1 2 3 4 mhdo …</aplcl>    is interpreted as having a left hyperand ('''short''' left scope) of <aplcl>4</aplcl> and a left operand ('''long''' left scope) of <aplcl>1 2 3</aplcl>.
			* A dyadic hyperator written as    <aplcl>… dhmo 1 2 3 4</aplcl>    is interpreted as having a right hyperand ('''short''' right scope) of <aplcl>1</aplcl> and a right argument ('''long''' right scope) of <aplcl>2 3 4</aplcl>.
			* A dyadic hyperator written as    <aplcl>… dhdo 1 2 3 4</aplcl>    is interpreted as having a right hyperand ('''short''' right scope) of <aplcl>1</aplcl>, a right operand ('''short''' right scope) of <aplcl>2</aplcl>, and a right argument ('''long''' right scope) of <aplcl>3 4</aplcl>.

			To reduce confusion, use parentheses such as <aplcl>(LO (LH dhdo 1) 2) 3 4</aplcl>.

	Abbreviations:		Abbreviations:

WikiSysop: /* Vector Notation */

2019-03-22T14:54:20Z

Vector Notation

← Older revision		Revision as of 10:54, 22 March 2019
Line 47:		Line 47:

	* A dyadic operator written as <apll>… dop 1 2 3</apll> is interpreted as having a right operand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.		* A dyadic operator written as <apll>… dop 1 2 3</apll> is interpreted as having a right operand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.
	* A hyperator written as <apll>1 2 3 mhmo</apll> is interpreted as having a left hyperand ('''short''' left scope) of <apll>3</apll> and a left operand ('''long''' left scope) of <apll>1 2</apll>.		* A hyperator written as either <apll>1 2 3 mhmo</apll> or <apll>1 2 3 mhdo …</apll> is interpreted as having a left hyperand ('''short''' left scope) of <apll>3</apll> and a left operand ('''long''' left scope) of <apll>1 2</apll>.
	* A dyadic hyperator written as <apll>… dhmo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.		* A dyadic hyperator written as <apll>… dhmo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.
	* A dyadic hyperator written as <apll>… dhdo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll>, a right operand ('''short''' right scope) of <apll>2</apll>, and a right argument of <apll>3</apll>.		* A dyadic hyperator written as <apll>… dhdo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll>, a right operand ('''short''' right scope) of <apll>2</apll>, and a right argument of <apll>3</apll>.

	To reduce confusion, use parentheses such as <apll>(LO (LH dhdo 1) 2) 3</apll>.		To reduce confusion, use parentheses such as <apll>(LO (LH dhdo 1) 2) 3</apll>.

			Abbreviations:
			* <apll>dop</apll> Dyadic Operator
			* <apll>mhmo</apll> Monadic Hyperand Monadic Operand Hyperator
			* <apll>mhdo</apll> Monadic Hyperand Dyadic Operand ...
			* <apll>dhmo</apll> Dyadic Hyperand Monadic Operand ...
			* <apll>dhdo</apll> Dyadic Hyperand Dyadic Operand ...

WikiSysop: /* Table */

2019-03-21T22:22:59Z

Table

← Older revision		Revision as of 18:22, 21 March 2019
Line 27:		Line 27:
	\|align="right"\| 4: \|\| Left operand \|\| Operator to its left operand \|\| <apll>"? MOP"</apll>		\|align="right"\| 4: \|\| Left operand \|\| Operator to its left operand \|\| <apll>"? MOP"</apll>
	\|-		\|-
	\|align="right"\| 4: \|\| ~~Trains~~ to right paren \|\| \|\| <apll>"… F)"</apll>		\|align="right"\| 4: \|\| Train right \|\| Train to its right paren \|\| <apll>"… F)"</apll>
	\|-		\|-
	\|align="right"\| 3: \|\| ~~Left paren to Trains~~ \|\| \|\| <apll>"(F …"</apll>		\|align="right"\| 3: \|\| Train left \|\| Train to its left paren \|\| <apll>"(F …"</apll>
	\|-		\|-
	\|align="right"\| 3: \|\| Left argument \|\| Function to its left argument \|\| <apll>"A F"</apll>		\|align="right"\| 3: \|\| Left argument \|\| Function to its left argument \|\| <apll>"A F"</apll>

WikiSysop: /* Table */

2019-03-21T21:12:24Z

Table

← Older revision		Revision as of 17:12, 21 March 2019
Line 1:		Line 1:
	==Table==		==Table==

	The rules for how Variables, Functions, Operators, ~~and~~ Hyperators and other syntactic elements combine are covered in the following table:		The rules for how Variables, Functions, Operators, Hyperators and other syntactic elements combine are covered in the following table:

	{\| border="1" cellspacing="0" cellpadding="5"		{\| border="1" cellspacing="0" cellpadding="5"

WikiSysop: /* Table */

2019-03-21T21:11:22Z

Table

← Older revision		Revision as of 17:11, 21 March 2019
Line 1:		Line 1:
	==Table==		==Table==

	The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table:		The rules for how Variables, Functions, Operators, and Hyperators and other syntactic elements combine are covered in the following table:

	{\| border="1" cellspacing="0" cellpadding="5"		{\| border="1" cellspacing="0" cellpadding="5"

WikiSysop at 21:10, 21 March 2019

2019-03-21T21:10:04Z

← Older revision		Revision as of 17:10, 21 March 2019
Line 1:		Line 1:
	=~~Binding Strength~~=		==Table==

	The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table:		The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table:
Line 9:		Line 9:
	!Example		!Example
	\|-		\|-
	\|align="right"\|12: \|\| Brackets left \|\| Brackets to what is on their left \|\| <apll>"? [..]"</apll>		\|align="right"\|12: \|\| Brackets left \|\| Brackets to what is on their left \|\| <apll>"? […]"</apll>
	\|-		\|-
	\|align="right"\|11: \|\| Specification left \|\| Left arrow to what is on its left \|\| <apll>"? ←"</apll>		\|align="right"\|11: \|\| Specification left \|\| Left arrow to what is on its left \|\| <apll>"? ←"</apll>
Line 27:		Line 27:
	\|align="right"\| 4: \|\| Left operand \|\| Operator to its left operand \|\| <apll>"? MOP"</apll>		\|align="right"\| 4: \|\| Left operand \|\| Operator to its left operand \|\| <apll>"? MOP"</apll>
	\|-		\|-
	\|align="right"\| 4: \|\| Trains to right paren \|\| \|\| <apll>"~~...~~ F)"</apll>		\|align="right"\| 4: \|\| Trains to right paren \|\| \|\| <apll>"… F)"</apll>
	\|-		\|-
	\|align="right"\| 3: \|\| Left paren to Trains \|\| \|\| <apll>"(F ~~...~~"</apll>		\|align="right"\| 3: \|\| Left paren to Trains \|\| \|\| <apll>"(F …"</apll>
	\|-		\|-
	\|align="right"\| 3: \|\| Left argument \|\| Function to its left argument \|\| <apll>"A F"</apll>		\|align="right"\| 3: \|\| Left argument \|\| Function to its left argument \|\| <apll>"A F"</apll>
Line 37:		Line 37:
	\|align="right"\| 1: \|\| Specification right \|\| Left arrow to what is on its right \|\| <apll>"← ?"</apll>		\|align="right"\| 1: \|\| Specification right \|\| Left arrow to what is on its right \|\| <apll>"← ?"</apll>
	\|-		\|-
	\|align="right"\| 0: \|\| Brackets right \|\| Brackets to what is on their right \|\| <apll>"[~~...~~] ?"</apll>		\|align="right"\| 0: \|\| Brackets right \|\| Brackets to what is on their right \|\| <apll>"[…] ?"</apll>
	\|}		\|}

			One way to look at these rules is that if you are given three names and/or symbols, you can always tell whether the middle object binds to the left or right object.

			==Vector Notation==

			As the above table indicates, Vector Notation has a lower Binding Strength than both a right operand to its operator and either hyperand to its hyperator. One consequence of this is a change introduced in NARS2000 Version 0.5.10 w.r.t. Numeric Strands. In particular,

			* A dyadic operator written as <apll>… dop 1 2 3</apll> is interpreted as having a right operand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.
			* A hyperator written as <apll>1 2 3 mhmo</apll> is interpreted as having a left hyperand ('''short''' left scope) of <apll>3</apll> and a left operand ('''long''' left scope) of <apll>1 2</apll>.
			* A dyadic hyperator written as <apll>… dhmo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll> and a right argument of <apll>2 3</apll>.
			* A dyadic hyperator written as <apll>… dhdo 1 2 3</apll> is interpreted as having a right hyperand ('''short''' right scope) of <apll>1</apll>, a right operand ('''short''' right scope) of <apll>2</apll>, and a right argument of <apll>3</apll>.

			To reduce confusion, use parentheses such as <apll>(LO (LH dhdo 1) 2) 3</apll>.

WikiSysop: Created page with "=Binding Strength= The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table: {| border="1" cellspacing="0" cellpadding="5" !# !Ca..."

2019-03-19T21:26:39Z

Created page with "=Binding Strength= The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table: {| border="1" cellspacing="0" cellpadding="5" !# !Ca..."

New page

=Binding Strength=

The rules for how Variables, Functions, Operators, and Hyperators are covered in the following table:

{| border="1" cellspacing="0" cellpadding="5"
!#
!Category
!Description
!Example
|-
|align="right"|12: || Brackets left || Brackets to what is on their left || <apll>"? [..]"</apll>
|-
|align="right"|11: || Specification left || Left arrow to what is on its left || <apll>"? ←"</apll>
|-
|align="right"|10: || Right hyperand, right operand || Dyadic hyperator to its right hyperand || <apll>"HYP ?"</apll>
|-
|align="right"| 9: || Right hyperand, left operand || Dyadic hyperator to its right hyperand || <apll>"HYP ?"</apll>
|-
|align="right"| 8: || Left hyperand, right operand || Hyperator to its left hyperand || <apll>"? HYP"</apll>
|-
|align="right"| 7: || Left hyperand, left operand || Hyperator to its left hyperand || <apll>"? HYP"</apll>
|-
|align="right"| 6: || Right operand || Dyadic operator to its right operand || <apll>"DOP ?"</apll>
|-
|align="right"| 5: || Vector notation || Array to an array || <apll>"A A"</apll>
|-
|align="right"| 4: || Left operand || Operator to its left operand || <apll>"? MOP"</apll>
|-
|align="right"| 4: || Trains to right paren || || <apll>"... F)"</apll>
|-
|align="right"| 3: || Left paren to Trains || || <apll>"(F ..."</apll>
|-
|align="right"| 3: || Left argument || Function to its left argument || <apll>"A F"</apll>
|-
|align="right"| 2: || Right argument || Function to its right argument || <apll>"F A"</apll>
|-
|align="right"| 1: || Specification right || Left arrow to what is on its right || <apll>"← ?"</apll>
|-
|align="right"| 0: || Brackets right || Brackets to what is on their right || <apll>"[...] ?"</apll>
|}