FAQ on Bridges/en - Versionsgeschichte

Cg: /* How are Bridges Started */

2026-04-16T13:27:00Z

How are Bridges Started

← Nächstältere Version		Version vom 16. April 2026, 13:27 Uhr
Zeile 23:		Zeile 23:
	== How are Bridges Started ==		== How are Bridges Started ==

	Bridges on the local machine are usually automatically started by expecco itself, when the first bridged action is executed (and stays alive, until expecco is terminated, or bridge connections are closed via the menu or via an expecco action block). Some language interpreters may take a few seconds to come up, so the first such action will execute relatively slow compared to later actions. You can add a dummy (empty) bridged action to your startup actions (project's postLoad action) to prepare the bridged interpreter.		Bridges on the local machine are usually automatically started by expecco itself, when the first bridged action is executed (and stays alive, until expecco is terminated, or bridge connections are closed via the menu or via an expecco action block). Some language interpreters may take a few seconds to come up, so the first such action will execute relatively slow compared to later actions. You can add a dummy (empty) bridged action to your startup actions (project's postLoad action) to prepare the bridged interpreter and have it startup in parallel.

	Bridges on other machines, or additional bridges on the local machine must be started by executing a bridge start action block or simply by executing a shell/batch action to call the corresponding language interpreter (python, node, etc.). On Windows, a powershell action can be used for remote execution (given that your Windows security settings allow that). On Unix, a shell action executin a remote shell / ssh command could be used.		Bridges on other machines, or additional bridges on the local machine must be started by executing a bridge start action block or simply by executing a shell/batch action to call the corresponding language interpreter (python, node, etc.). On Windows, a powershell action can be used for remote execution (given that your Windows security settings allow that). On Unix, a shell action executin a remote shell / ssh command could be used.

Cg: /* How can I debug the code in the bridge */

2023-10-18T11:45:56Z

How can I debug the code in the bridge

← Nächstältere Version		Version vom 18. Oktober 2023, 11:45 Uhr
Zeile 190:		Zeile 190:

	== How can I debug the code in the bridge ==		== How can I debug the code in the bridge ==
	Expecco does include some debugging support for bridged code, but the level of support is different between individual bridges:		Expecco does include some limited debugging support for bridged code, but the level of support is different between individual bridges:
	* Python, Node, Smalltalk, Groovy<br>Support breakpoints and single stepping. Walkback and some access to remote objects.		* Python, Node, Smalltalk, Groovy<br>Support breakpoints and single stepping. Walkback and some access to remote objects.
	* C<br>Walkback and some access to remote objects.		* C<br>Walkback and some access to remote objects.

Cg: /* What can I do if a Bridge is Dead(locked) */

2023-10-18T11:42:06Z

What can I do if a Bridge is Dead(locked)

← Nächstältere Version		Version vom 18. Oktober 2023, 11:42 Uhr
Zeile 94:		Zeile 94:
	* select "''Extras''" → "''Debugging''" → "''Close all Bridge Connections''"<br>This will terminate all running bridges (maybe this is not what you want)		* select "''Extras''" → "''Debugging''" → "''Close all Bridge Connections''"<br>This will terminate all running bridges (maybe this is not what you want)
	* select "''Extras''" → "''Debugging''" → "''OS Process Monitor''" to get a list of all OS processes which have been started by expecco, select the one to terminate and choose "''Terminate''" from the context menu.		* select "''Extras''" → "''Debugging''" → "''OS Process Monitor''" to get a list of all OS processes which have been started by expecco, select the one to terminate and choose "''Terminate''" from the context menu.
			* select and terminate the bridge process in the Task Manager (Windows) or find its processID with the "ps" command and terminate it via the "kill" command (Unix)

	If the bridge was not originally started by expecco (eg. if it is a remote bridge, which was started automatically or by a remote command), you have to log into that remote machine and ~~termiante~~ the bridge there.		If the bridge was not originally started by expecco (eg. if it is a remote bridge, which was started automatically or by a remote command), you have to log into that remote machine and terminate the bridge there.

	In a production system, you may add time limits to actions which might suffer from locked bridges, and add a bridge-terminate action (found in the Standard Library) to be triggered via the exception pin of the time-controlled action.		In a production system, you may add time limits to actions which might suffer from locked bridges, and add a bridge-terminate action (found in the Standard Library) to be triggered via the exception pin of the time-controlled action.

Cg: /* What are Proxy Objects */

2023-10-18T11:38:19Z

What are Proxy Objects

← Nächstältere Version		Version vom 18. Oktober 2023, 11:38 Uhr
Zeile 59:		Zeile 59:

	== What are Proxy Objects ==		== What are Proxy Objects ==
	These are placeholder objects inside expecco, which will look like regular Smalltalk (or JavaScript) objects inside expecco, but will forward any call ~~over~~ via the socket to the bridge partner.		These are placeholder objects inside expecco, which will look like regular Smalltalk (or JavaScript) objects inside expecco, but will forward any call via the socket ower to the bridge partner.

	Thus, they can be used transparently inside Smalltalk and JavaScript elementary actions, performing whatever is implemented in the remote side.		Thus, they can be used transparently inside Smalltalk and JavaScript elementary actions, performing whatever is implemented in the remote side.

Cg: /* Ports Used for Bridge Communication */

2023-10-18T11:37:40Z

Ports Used for Bridge Communication

← Nächstältere Version		Version vom 18. Oktober 2023, 11:37 Uhr
Zeile 45:		Zeile 45:
	Node 8577 , 8578 (debug)		Node 8577 , 8578 (debug)
	Electron 8588 , 8589 (debug)		Electron 8588 , 8589 (debug)
	[[Embedded_Systems_C_Bridge_API \|CBridge]] 8855		[[Embedded_Systems_C_Bridge_API \|CBridge]] 8855 (also for Root/Cling)
	Smalltalk 8877		Smalltalk 8877
	VASmalltalk 8879		VASmalltalk 8879
	VWSmalltalk 8881		VWSmalltalk 8881
	Root/Cling. 8883
	Dart 8885		Dart 8885
	Ruby 8977		Ruby 8977

Cg: /* Ports Used for Bridge Communication */

2023-10-18T11:35:59Z

Ports Used for Bridge Communication

← Nächstältere Version		Version vom 18. Oktober 2023, 11:35 Uhr
Zeile 46:		Zeile 46:
	Electron 8588 , 8589 (debug)		Electron 8588 , 8589 (debug)
	[[Embedded_Systems_C_Bridge_API \|CBridge]] 8855		[[Embedded_Systems_C_Bridge_API \|CBridge]] 8855
⚫	Root/Cling. 8883
	Smalltalk 8877		Smalltalk 8877
	VASmalltalk 8879		VASmalltalk 8879
	VWSmalltalk 8881		VWSmalltalk 8881
		⚫	Root/Cling. 8883
			Dart 8885
			Ruby 8977
			Scheme 8599

	Note: for some bridges, two connections are used, the debug port being used by the debugger to inspect data and to support breakpoints, single stepping etc.		Note: for some bridges, two connections are used, the debug port being used by the debugger to inspect data and to support breakpoints, single stepping etc.

Cg: /* Which Languages are Supported */

2023-10-18T11:28:33Z

Which Languages are Supported

← Nächstältere Version		Version vom 18. Oktober 2023, 11:28 Uhr
Zeile 14:		Zeile 14:
	* Java (using either Groovy or Jython as "''glue''" or directly using proxy objects in expecco)		* Java (using either Groovy or Jython as "''glue''" or directly using proxy objects in expecco)
	* Python (both Python 2.7 and Python 3.x)		* Python (both Python 2.7 and Python 3.x)
	* .NET (using IronPython as "''glue''" or directly in via proxy objects)		* .NET (using IronPython as "''glue''" or directly via proxy objects)
	* NodeJS		* NodeJS (i.e. JavaScript)
	* C/C++ (Root/Cling is being developed currently)		* C/C++ (Root/Cling is being developed currently)
	* Smalltalk (Smalltalk/X and VisualWorks are currently supported; VisualAge may come in the near future, if there is sufficient customer interest)		* Smalltalk (Smalltalk/X and VisualWorks are currently supported; VisualAge may come in the near future, if there is sufficient customer interest)
			* Ruby
	Plans are to support ~~Ruby~~ and Scheme in the future.		Plans are to support Dart and Scheme in the future.

	== How are Bridges Started ==		== How are Bridges Started ==

Cg: /* Which Languages are Supported */

2023-10-18T11:27:03Z

Which Languages are Supported

← Nächstältere Version		Version vom 18. Oktober 2023, 11:27 Uhr
Zeile 12:		Zeile 12:

	By the time this chapter was written, bridged code execution is supported for:		By the time this chapter was written, bridged code execution is supported for:
	* Java (using either Groovy or ~~jPython~~ as "''glue''" or directly using proxy objects in expecco)		* Java (using either Groovy or Jython as "''glue''" or directly using proxy objects in expecco)
	* Python (both Python 2.7 and Python 3.x)		* Python (both Python 2.7 and Python 3.x)
	* .NET (using IronPython as "''glue''" or directly in via proxy objects)		* .NET (using IronPython as "''glue''" or directly in via proxy objects)

Cg: /* Security Considerations */

2023-06-21T19:33:22Z

Security Considerations

← Nächstältere Version		Version vom 21. Juni 2023, 19:33 Uhr
Zeile 199:		Zeile 199:

	== Security Considerations ==		== Security Considerations ==
	Make sure that remote bridges are only reachable from inside your local network and only from trusted hosts. You should configure your firewall as appropriate, or run tests in an isolated network. ~~All~~ ~~bridges~~ ~~support~~ ~~command~~ ~~line~~ ~~arguments~~ to ~~only~~ ~~accept~~ ~~connections~~ ~~from~~ a ~~particular~~ ~~host;~~ ~~this option should be used if a remote bridge is started via a~~ ~~remote~~ ~~shell~~ ~~command~~.		Make sure that remote bridges are only reachable from inside your local network and only from trusted hosts. You should configure your firewall as appropriate, or run tests in an isolated network. You may also configure switches and routers to limit access, or use a secondary interface (alternative lan or wifi).

			Another recommened option is to setup an ssh tunnel for the particular port(s) in question.

			All bridges support command line arguments to only accept connections from a particular host; this option should be used if a remote bridge is started via a remote shell command.

	== [OS X Only] CrashReporter Dialog Boxes ==		== [OS X Only] CrashReporter Dialog Boxes ==

Cg: /* I don't see the difference between DLL actions and bridged C-actions; when to use which? */

2023-06-21T19:19:42Z

I don't see the difference between DLL actions and bridged C-actions; when to use which?

← Nächstältere Version		Version vom 21. Juni 2023, 19:19 Uhr
Zeile 169:		Zeile 169:
	<br>'''(-)''' the called code may crash the expecco executable if it misbehaves or is provided with wrong arguments<BR>(notice: although expecco tries to catch any illegal memory references, it may still happen, that a called DLL-function misbehaves and overwrites/manipulates memory which it is not supposed to. For example, if it overwrites any data of expecco, there may be a later crash in expecco.		<br>'''(-)''' the called code may crash the expecco executable if it misbehaves or is provided with wrong arguments<BR>(notice: although expecco tries to catch any illegal memory references, it may still happen, that a called DLL-function misbehaves and overwrites/manipulates memory which it is not supposed to. For example, if it overwrites any data of expecco, there may be a later crash in expecco.
	<br>'''(-)''' the called code may block expecco or slow down the user interface		<br>'''(-)''' the called code may block expecco or slow down the user interface
	<br>'''(-)''' the called code may exit/terminate the current thread or the program and thus terminate expecco (i.e. make sure, it does not call "<code>exit()</code>"		<br>'''(-)''' the called code may exit/terminate the current thread or the program and thus terminate expecco (i.e. make sure, it does not call "<code>exit()</code>"). Although expecco sets the "atexit" handler, shared libraries may still find other means to terminate.

	Bridged Calls:		Bridged Calls: