ElementaryBlock Element/en - Versionsgeschichte

Cg: /* Standard Input / Standard Output Handling */

2026-02-26T13:59:38Z

Standard Input / Standard Output Handling

← Nächstältere Version		Version vom 26. Februar 2026, 13:59 Uhr
Zeile 475:		Zeile 475:
	These pins can be configured to either provide the whole output as one big string, or linewise either as individual lines or as chunks of multiple lines.		These pins can be configured to either provide the whole output as one big string, or linewise either as individual lines or as chunks of multiple lines.

	[[Datei:bulb.png\|16px]] Notice, that those pins are hidden by default, you have to add them via the action's context menu ("''Special Pins''").		[[Datei:bulb.png\|16px]] Notice, that those pins are hidden by default, you have to add them via the action's context menu ("''Special Pins''") in the schema page.

	===== Buffered vs. Unbuffered Stdout and Stderr =====		===== Buffered vs. Unbuffered Stdout and Stderr =====

Cg: /* Script Execution in General */

2026-02-26T13:58:16Z

Script Execution in General

← Nächstältere Version		Version vom 26. Februar 2026, 13:58 Uhr
Zeile 467:		Zeile 467:
	=== Script Execution in General ===		=== Script Execution in General ===

	The following sections describe the mechanism of script blocks in general, all of this is valid for Shell, Batch and all the other external scripting language action blocks (i.e. python, ruby, tcl, etc.). Be reminded that there is a fundamental difference between ''script actions'' and ''bridged actions'' as described above.		The following sections describe the mechanism of script blocks in general, all of this is valid for Shell, Batch and all the other external scripting language action blocks (i.e. python, ruby, tcl, etc.). Be reminded that there is a fundamental difference between ''script actions'' and [[#Bridged_Actions \| ''bridged actions'']] as described above.

	==== Standard Input / Standard Output Handling ====		==== Standard Input / Standard Output Handling ====

Cg: /* Smalltalk Blocks (Bridged) */

2025-05-10T19:14:25Z

Smalltalk Blocks (Bridged)

← Nächstältere Version		Version vom 10. Mai 2025, 19:14 Uhr
Zeile 449:		Zeile 449:

	The API is described in the [[Expecco_API#Bridged_Smalltalk_Elementary_Blocks\|"Expecco API documentation on Bridged Smalltalk Actions"]].		The API is described in the [[Expecco_API#Bridged_Smalltalk_Elementary_Blocks\|"Expecco API documentation on Bridged Smalltalk Actions"]].

			== Scheme Blocks (Bridged) ==

			Experimental and Unfinished
			Bridged Scheme actions are executed by a separate Scheme process, either on the local machine, or on a remote machine. As with the other bridge implementations, the code is dynamically transported to the target virtual machine and executed there.

			Currently, bridged Scheme execution is supported for GNU-Scheme and Racket/MZScheme.

			The API is described in the [[Expecco_API#Bridged_Scheme_Elementary_Blocks\|"Expecco API documentation on Bridged Scheme Actions"]].

	== Script Action Blocks ==		== Script Action Blocks ==

Cg: /* R Action Blocks */

2025-05-10T16:05:24Z

R Action Blocks

← Nächstältere Version		Version vom 10. Mai 2025, 16:05 Uhr
Zeile 872:		Zeile 872:
	Concrete examples are found in the library "<code>Plot_Graph_Library.ets</code>", which is found in the gnuplot plugin or the demos folder.		Concrete examples are found in the library "<code>Plot_Graph_Library.ets</code>", which is found in the gnuplot plugin or the demos folder.

	=== R ~~Action~~ Blocks ===		=== R Script Blocks ===

	With expecco rel18.1, another new action type was added for 'R' action blocks.		With expecco rel18.1, another new action type was added for 'R' action blocks.

Cg: /* Python Script Blocks */

2025-04-04T14:02:31Z

Python Script Blocks

← Nächstältere Version		Version vom 4. April 2025, 14:02 Uhr
Zeile 772:		Zeile 772:
	You have to ensure that an appropriate Python interpreter is installed on the machine (it is not part of the expecco delivery package).		You have to ensure that an appropriate Python interpreter is installed on the machine (it is not part of the expecco delivery package).

	Similar to shell scripts, the Python interpreter path can be either be left unspecified,		Similar to shell scripts, the Python interpreter path can be either left unspecified,
	or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "PYTHON_SHELL").		or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "PYTHON_SHELL").
	The environment variable can be in any environment which is visible in the scope of the Python action.		The environment variable can be in any environment which is visible in the scope of the Python action.

Cg: /* Scheme Script Blocks */

2025-04-04T14:01:59Z

Scheme Script Blocks

← Nächstältere Version		Version vom 4. April 2025, 14:01 Uhr
Zeile 948:		Zeile 948:
	You have to ensure that an appropriate Scheme interpreter is installed on the machine (it is not part of the expecco delivery package).		You have to ensure that an appropriate Scheme interpreter is installed on the machine (it is not part of the expecco delivery package).

	Similar to python scripts, the Scheme interpreter path can be either be left unspecified,		Similar to python scripts, the Scheme interpreter path can be either left unspecified,
	or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "SCHEME_SHELL").		or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "SCHEME_SHELL").
	The environment variable can be in any environment which is visible in the scope of the Scheme action.		The environment variable can be in any environment which is visible in the scope of the Scheme action.

Cg: /* Specifying the Dialect in the Script */

2025-04-04T12:50:40Z

Specifying the Dialect in the Script

← Nächstältere Version		Version vom 4. April 2025, 12:50 Uhr
Zeile 972:		Zeile 972:
	If the very first line of your script is (exactly as written, without any whitespace at the left or in between the semi and the identifier) one of:		If the very first line of your script is (exactly as written, without any whitespace at the left or in between the semi and the identifier) one of:
	;RACKET		;RACKET

	;CHEZ		;CHEZ
			;CHICKEN

	;GUILE		;GUILE

	;SCHTEAM		;SCHTEAM
	then the script will ignore any environment values and executed with that dialect's setup values (see Scheme settings).		then the script will ignore any environment values and executed with that dialect's setup values (see Scheme settings).

Cg: /* Scheme Script Blocks */

2025-04-04T12:50:15Z

Scheme Script Blocks

← Nächstältere Version		Version vom 4. April 2025, 12:50 Uhr
Zeile 953:		Zeile 953:
	If left unspecified, or without an absolute path, the Scheme interpreter should be found along the PATH by the name "scheme".		If left unspecified, or without an absolute path, the Scheme interpreter should be found along the PATH by the name "scheme".

	As with other script blocks, ~~SCheme~~ script blocks provide the standard output and standard error at their output pins as text, so you may have to read and analyze that further. You can also send values to output pins or messages to the activity log by sending an appropriate string to stderr (as described above).		As with other script blocks, Scheme script blocks provide the standard output and standard error at their output pins as text, so you may have to read and analyze that further. You can also send values to output pins or messages to the activity log by sending an appropriate string to stderr (as described above).
	<br>For details and examples, please refer to the "[[ #Script Execution in General \|Script Execution in General]]" section above.		<br>For details and examples, please refer to the "[[ #Script Execution in General \|Script Execution in General]]" section above.

Cg: /* Go Script Blocks */

2025-04-04T12:49:34Z

Go Script Blocks

← Nächstältere Version		Version vom 4. April 2025, 12:49 Uhr
Zeile 941:		Zeile 941:

	Same as [[#Script_Execution_in_General\|above]]..		Same as [[#Script_Execution_in_General\|above]]..

			=== Scheme Script Blocks ===

			These are execute by an external [https://www.scheme.org scheme language interpreter].

			You have to ensure that an appropriate Scheme interpreter is installed on the machine (it is not part of the expecco delivery package).

			Similar to python scripts, the Scheme interpreter path can be either be left unspecified,
			or specified in the expecco settings ("''external tools''"), or via an expecco environment variable named "SCHEME_SHELL").
			The environment variable can be in any environment which is visible in the scope of the Scheme action.
			If left unspecified, or without an absolute path, the Scheme interpreter should be found along the PATH by the name "scheme".

			As with other script blocks, SCheme script blocks provide the standard output and standard error at their output pins as text, so you may have to read and analyze that further. You can also send values to output pins or messages to the activity log by sending an appropriate string to stderr (as described above).
			<br>For details and examples, please refer to the "[[ #Script Execution in General \|Script Execution in General]]" section above.

			===== Scheme Dialects =====
			There are many scheme dialects found, and they are not all compatible to each other.
			It may be necessary to specify an explicit Scheme dialect to be used for script actions.

			If all of your actions depend on the same interpreter,
			it is sufficient to ensure that either the "<code>SCHEME_SHELL</code>" variable is set correctly,
			or the "Scheme Path" is defined in the settings to point to the correct interpreter.
			However, if you have mixed version scripts (for example, when importing actions written by another team, which used a different dialect), you have to specify the Scheme interpreter explicitly for some of the actions.

			This can be done either by specifying the version explicitly in the script itself,
			or indirectly, via an environment variable.

			===== Specifying the Dialect in the Script =====

			If the very first line of your script is (exactly as written, without any whitespace at the left or in between the semi and the identifier) one of:
			;RACKET

			;CHEZ

			;GUILE

			;SCHTEAM
			then the script will ignore any environment values and executed with that dialect's setup values (see Scheme settings).

			===== Specifying the Dialect in an Environment Variable =====


			A variable named "SCHEME_DIALECT" should be defined, which holds one of the above dialect names"<code>RACKET</code>", "<code>CHEZ</code>" etc. This specification will be used.

			The Settings or a corresponding variable then define the interpreter (in "''Settings''" -> "''Execution''" -> "''External Language Interpreters''"):
			* "Scheme Path" in the settings or the "<code>SCHEME_SHELL</code>" shell environment variable,<br>are used when no explicit dialect is specified,
			* "Racket Path" in the settings (or the "<code>RACKET_SCHEME_SHELL</code>" shell variable)<br>are used for scripts which have been marked as explicitly requiring racket,
			* and so on


			Using that double-indirect mechanism, it is still possible to:
			* import multiple libraries with different python-versions requirements
			* specify the paths independent of where the Python interpreters are installed (i.e. the machine on which the final suite is executed may have different installation paths than the machine on which the imported libraries were developed).

	=== Any other Scripting Language via Shell Blocks ===		=== Any other Scripting Language via Shell Blocks ===

Cg: /* C# Action Blocks */

2025-01-09T09:59:12Z

C# Action Blocks

← Nächstältere Version		Version vom 9. Januar 2025, 09:59 Uhr
Zeile 368:		Zeile 368:
	Similar to Groovy actions, these are bridged actions, executed inside a .NET Virtual Machine (CLR), either locally, on a remote system or inside the system under test (SUT). It is possible to define new classes, new functions and to create objects which persist between C# calls. It is also possible to define callbacks and other functions which lead back into expecco. C# actions are described in more detail in the [[ Expecco_API \| Expecco API documentation ]] .		Similar to Groovy actions, these are bridged actions, executed inside a .NET Virtual Machine (CLR), either locally, on a remote system or inside the system under test (SUT). It is possible to define new classes, new functions and to create objects which persist between C# calls. It is also possible to define callbacks and other functions which lead back into expecco. C# actions are described in more detail in the [[ Expecco_API \| Expecco API documentation ]] .

	C# source code entry will be available with ~~the~~ ~~20.1~~ version. However the basic mechanism to call .NET functions and exchange objects is already present and used in various places. The code is currently written in Smallalk or JavaScript, using the call forwarding mechanisms provided by Smalltalk. An alternative mechanism to interface to CLR-assemplies is via IronPython as described below.		C# source code entry will be available with a future version. However the basic mechanism to call .NET functions and exchange objects is already present and used in various places. The code is currently written in Smallalk or JavaScript, using the call forwarding mechanisms provided by Smalltalk. An alternative mechanism to interface to CLR-assemplies is via IronPython as described below.

	== Node.js Blocks (Bridged) ==		== Node.js Blocks (Bridged) ==