Scripting Language Syntax - Revision history

Nairnj: /* Differences in the NairnFEAMPMViz Scripting Language */

2019-08-12T23:15:36Z

Differences in the NairnFEAMPMViz Scripting Language

← Older revision		Revision as of 23:15, 12 August 2019
Line 267:		Line 267:

	# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.		# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.
	~~# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes~~

	~~Besides~~ the ~~above difference~~, ~~some features of~~ the ~~scripting language are not yet available in [[~~NairnFEAMPMViz~~]], although they are planned~~ to be ~~added in~~ the ~~future~~. The ~~unsupported features are:~~		If you get an error message suggesting a command that looks valid is an invalid command, check the delimiter between the command name and the first parameter. The NairnFEAMPM Mac program will work with any delimiter, but the NairnFEAMPMViz app requires the delimiter after commands to be one or more spaces. If a parameter is misinterpreted, look at delimiters between the parameters. The NairnFEAMPM Mac program will work with any delimiter, but this NairnFEAMPMViz app requires commas.

	~~# Two [[Expression Syntax#Supported Functions\|numeric functions]] for error functions are not available.~~

	~~When writing command files to use in both applications~~, ~~you should avoid anything not supported in both applications. The main recommendations are to~~

	~~# Because to use space between command and first argument and to use~~ commas ~~between all command arguments~~
	~~# Surround all plain text arguments in quotes~~.

Nairnj: /* Differences in the NairnFEAMPMViz Scripting Language */

2019-08-12T22:41:17Z

Differences in the NairnFEAMPMViz Scripting Language

← Older revision		Revision as of 22:41, 12 August 2019
Line 275:		Line 275:
	When writing command files to use in both applications, you should avoid anything not supported in both applications. The main recommendations are to		When writing command files to use in both applications, you should avoid anything not supported in both applications. The main recommendations are to

	# ~~Start~~ all ~~variables in a number sign (#).~~		# Because to use space between command and first argument and to use commas between all command arguments
	~~# End all variables with string content with a dollar sign ($).~~
	# Surround all plain text arguments in quotes.		# Surround all plain text arguments in quotes.
	~~# Do not use exponential numbers in expressions except for simple assignments (''e.g.'', #x=4.56e-3)~~

Nairnj: /* Differences in the NairnFEAMPMViz Scripting Language */

2019-08-12T22:40:06Z

Differences in the NairnFEAMPMViz Scripting Language

← Older revision		Revision as of 22:40, 12 August 2019
Line 267:		Line 267:

	# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.		# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.
	# Numeric [[Expression Syntax\|expressions]] can only use exponential numbers (''e.g.'', 4.56e-3) when they are the entire expression (''e.g.'', #x=4.56e-3). In [[NairnFEAMPM]], exponential numbers can be used any place a number can be used.
	# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes		# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes

Nairnj: /* Differences in the NairnFEAMPMViz Scripting Language */

2019-08-12T22:39:45Z

Differences in the NairnFEAMPMViz Scripting Language

← Older revision		Revision as of 22:39, 12 August 2019
Line 267:		Line 267:

	# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.		# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.
	# [[Variable Names\|Variables]] need not begin in a number sign (#), string variables must end in a dollar sign ($), numeric variable must not end in a dollar sign ($), and variable names cannot contain any [[Expression Syntax#Support Functions\|supported function]] as a substring in the name. In [[NairnFEAMPM]], all variables must begin in number sign (#) and no distinction need be made between numeric and string variables.
	# Numeric [[Expression Syntax\|expressions]] can only use exponential numbers (''e.g.'', 4.56e-3) when they are the entire expression (''e.g.'', #x=4.56e-3). In [[NairnFEAMPM]], exponential numbers can be used any place a number can be used.		# Numeric [[Expression Syntax\|expressions]] can only use exponential numbers (''e.g.'', 4.56e-3) when they are the entire expression (''e.g.'', #x=4.56e-3). In [[NairnFEAMPM]], exponential numbers can be used any place a number can be used.
	# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes		# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes

Nairnj: /* Differences in the NairnFEAMPMViz Scripting Language */

2016-12-26T20:06:04Z

Differences in the NairnFEAMPMViz Scripting Language

← Older revision		Revision as of 20:06, 26 December 2016
Line 267:		Line 267:

	# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.		# The main [[Command Line Syntax\|command on each line]] must be separated from arguments by a space and arguments must be delimited by commas. In [[NairnFEAMPM]] commands and arguments can be delimited by commas, spaces, or tabs.
	# [[Variable Names\|Variables]] need not begin in a number sign (#), string variables must end in a dollar sign ($), numeric variable must not end in a dollar sign ($), and variable names cannot contain any [[Expression Syntax#Support Functions\|supported function]] as a substring in the name.		# [[Variable Names\|Variables]] need not begin in a number sign (#), string variables must end in a dollar sign ($), numeric variable must not end in a dollar sign ($), and variable names cannot contain any [[Expression Syntax#Support Functions\|supported function]] as a substring in the name. In [[NairnFEAMPM]], all variables must begin in number sign (#) and no distinction need be made between numeric and string variables.
	# Numeric [[Expression Syntax\|expressions]] can only use exponential numbers (''e.g.'', 4.56e-3) when they are the entire expression (''e.g.'', #x=4.56e-3).		# Numeric [[Expression Syntax\|expressions]] can only use exponential numbers (''e.g.'', 4.56e-3) when they are the entire expression (''e.g.'', #x=4.56e-3). In [[NairnFEAMPM]], exponential numbers can be used any place a number can be used.
			# All plain-text arguments must be quoted. In [[NairnFEAMPM]], many uses of plain text will be accepted even without quotes

	Besides the above difference, some features of the scripting language are not yet available in [[NairnFEAMPMViz]], although they are planned to be added in the future. The unsupported features are:		Besides the above difference, some features of the scripting language are not yet available in [[NairnFEAMPMViz]], although they are planned to be added in the future. The unsupported features are:

	# Two [[Expression Syntax#Supported Functions\|numeric functions]] for error functions are not available.		# Two [[Expression Syntax#Supported Functions\|numeric functions]] for error functions are not available.
	~~# No [[Expression Syntax#Supported Functions\|string functions]] are available.~~

	When writing command files to use in both applications, you should avoid anything not supported in both applications. The main recommendations are to ~~start~~ all variables in # ~~and to end~~ string ~~variables~~ in $.		When writing command files to use in both applications, you should avoid anything not supported in both applications. The main recommendations are to

			# Start all variables in a number sign (#).
			# End all variables with string content with a dollar sign ($).
			# Surround all plain text arguments in quotes.
			# Do not use exponential numbers in expressions except for simple assignments (''e.g.'', #x=4.56e-3)

Nairnj: /* Words Command */

2016-12-26T19:49:08Z

Words Command

← Older revision		Revision as of 19:49, 26 December 2016
Line 215:		Line 215:
	If #1 is "#varName$", for example, the extracted words will be in #varName$[1], #varName$[2], etc., and the total number of words will be stored in #varName$[0].		If #1 is "#varName$", for example, the extracted words will be in #varName$[1], #varName$[2], etc., and the total number of words will be stored in #varName$[0].

	If optional #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces (''i.e.'', any length whitespace). When #5 is a space (" "), each space is a delimiter with words between adjacent spaces ~~being a~~ zero-length ~~string~~.		If optional #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces (''i.e.'', any length whitespace). When #5 is a space (" "), each space is a delimiter with words between adjacent spaces become zero-length strings.

	==== Stop Command ====		==== Stop Command ====

Nairnj: /* Words Command */

2016-12-26T19:48:46Z

Words Command

← Older revision		Revision as of 19:48, 26 December 2016
Line 215:		Line 215:
	If #1 is "#varName$", for example, the extracted words will be in #varName$[1], #varName$[2], etc., and the total number of words will be stored in #varName$[0].		If #1 is "#varName$", for example, the extracted words will be in #varName$[1], #varName$[2], etc., and the total number of words will be stored in #varName$[0].

	If optional #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces. When #5 is a space (" "), each space is a delimiter with words between adjacent spaces being a zero-length string.		If optional #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces (''i.e.'', any length whitespace). When #5 is a space (" "), each space is a delimiter with words between adjacent spaces being a zero-length string.

	==== Stop Command ====		==== Stop Command ====

Nairnj: /* Words Command */

2016-12-26T19:47:30Z

Words Command

← Older revision		Revision as of 19:47, 26 December 2016
Line 209:		Line 209:
	The <tt>Words</tt> command divides up a variable by words:		The <tt>Words</tt> command divides up a variable by words:

	Words#1,#2,#3,#4,<#5>		Words #1,#2,#3,#4,<#5>

	where #1 is a valid string variable name in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is a string possibly containing multiple words. #2 and #3 give word numbers (first word is word number 1) or can be <=0 to specify word number relative to the end (0 is last word, -1 is next to last, ''etc.'')		where #1 is a valid string variable name in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is a string possibly containing multiple words. #2 and #3 give word numbers (first word is word number 1) or can be <=0 to specify word number relative to the end (0 is last word, -1 is next to last, ''etc.'')

Nairnj: /* Words Command */

2016-12-25T06:43:44Z

Words Command

← Older revision		Revision as of 06:43, 25 December 2016
Line 211:		Line 211:
	Words#1,#2,#3,#4,<#5>		Words#1,#2,#3,#4,<#5>

	where #1 is a valid string variable ~~names~~ in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is string possibly containing multiple words. #2 and #3 give ~~wprdnumbers~~ (first word is word number 1) or can be <=0 to specify word number relative to the end (0 is last ~~line~~, -1 is next to last, ''etc.'')		where #1 is a valid string variable name in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is a string possibly containing multiple words. #2 and #3 give word numbers (first word is word number 1) or can be <=0 to specify word number relative to the end (0 is last word, -1 is next to last, ''etc.'')

	If #1 is "#varName$", for example, the extracted ~~wordswill~~ be in #varName$[1], #varName$[2], etc., and the total number of words will to stored in #varName$[0].		If #1 is "#varName$", for example, the extracted words will be in #varName$[1], #varName$[2], etc., and the total number of words will be stored in #varName$[0].

	If ~~options~~ #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces. When #5 is a space (" "), each space is a ~~delimit~~ with words between adjacent spaces being a zero-length string.		If optional #5 is used, the string in #4 is split by occurrences of #5. Note that setting #5 to a space (" ") is not the same as omitting number #5. When #5 is omitted, the words are split by one or more spaces. When #5 is a space (" "), each space is a delimiter with words between adjacent spaces being a zero-length string.

	==== Stop Command ====		==== Stop Command ====

Nairnj: /* Lines Command */

2016-12-25T06:40:04Z

Lines Command

← Older revision		Revision as of 06:40, 25 December 2016
Line 201:		Line 201:
	Lines #1,#2,#3,#4		Lines #1,#2,#3,#4

	where #1 is a valid string variable name in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is string possibly containing multiple lines. #2 and #3 give line numbers (first line is line number 1) or can be <=0 to specify line number relative to the end (0 is last line, -1 is next to last line, ''etc.'').		where #1 is a valid string variable name in quotes (''e.g.'', "#varName$"), #2 and #3 specify the range of lines to extract, and #4 is a string possibly containing multiple lines. #2 and #3 give line numbers (first line is line number 1) or can be <=0 to specify line number relative to the end (0 is last line, -1 is next to last line, ''etc.'').

	If #1 is "#varName$", for example, the extracted lines will be in #varName$[1], #varName$[2], ''etc.'', and the total number of lines will be stored in #varName$[0].		If #1 is "#varName$", for example, the extracted lines will be in #varName$[1], #varName$[2], ''etc.'', and the total number of lines will be stored in #varName$[0].