Perl Script Snippets - Revision history

Ivailop: /* Accessing compiler macro values (constants) */

2018-12-26T23:18:27Z

Accessing compiler macro values (constants)

← Older revision		Revision as of 23:18, 26 December 2018
Line 220:		Line 220:

	<source lang="perl">		<source lang="perl">
	my $value = ~~Remote~~->SOME_DEFINED_VALUE;		my $value = Constants->{SOME_DEFINED_VALUE};
	</source>		</source>

Ivailop at 23:39, 16 October 2018

2018-10-16T23:39:06Z

← Older revision		Revision as of 23:39, 16 October 2018
Line 5:		Line 5:

	* Windows		* Windows
	perl -I %STRIDE_DIR%\lib\perl -I %STRIDE_DIR%\lib\perl\5.10 -cw MyTests.pm		perl -I %STRIDE_DIR%\lib\perl -I %STRIDE_DIR%\lib\perl\5.20 -cw MyTests.pm

	* Linux/FreeBSD		* Linux/FreeBSD
	perl -I $STRIDE_DIR/lib/perl -I $STRIDE_DIR/lib/perl/5.10 -cw MyTests.pm		perl -I $STRIDE_DIR/lib/perl -I $STRIDE_DIR/lib/perl/5.20 -cw MyTests.pm

	This will compile the perl script without running it, and it will emit any syntax errors that are found.		This will compile the perl script without running it, and it will emit any syntax errors that are found.

Marku: /* Standalone two-line script for invoking a remote function */

2015-07-06T20:55:30Z

Standalone two-line script for invoking a remote function

← Older revision		Revision as of 20:55, 6 July 2015
Line 188:		Line 188:

	=== Standalone two-line script for invoking a remote function ===		=== Standalone two-line script for invoking a remote function ===
	This simple script shows the minimal code required to make a remote function call of a function that has been enabled with [[Function ~~Capturing#Remoting\|STRIDE remoting~~]].		This simple script shows the minimal code required to make a remote function call of a function that has been enabled with the [[Scl_function \| Function Pragrma]] enabling remoting.
	<source lang="perl">		<source lang="perl">
	use STRIDE;		use STRIDE;

Marku at 20:50, 6 July 2015

2015-07-06T20:50:59Z

← Older revision		Revision as of 20:50, 6 July 2015
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	Below are some brief examples of script test modules that use the [[Perl Script APIs]] for ~~STRIDE~~. Most of these examples are incomplete and are only intended to give a quick overview of how this API can be used.		Below are some brief examples of script test modules that use the [[Perl Script APIs]] for Stride. Most of these examples are incomplete and are only intended to give a quick overview of how this API can be used.

	With any perl module that you write, we recommend that you perform a quick syntax check before attempting to execute the module using the ~~STRIDE runner~~. Syntax checking with warnings is easily accomplished by running with the <tt>-cw</tt> option, e.g.:		With any perl module that you write, we recommend that you perform a quick syntax check before attempting to execute the module using the Stride Runner. Syntax checking with warnings is easily accomplished by running with the <tt>-cw</tt> option, e.g.:

	* Windows		* Windows

Marku at 18:39, 2 July 2015

2015-07-02T18:39:11Z

← Older revision		Revision as of 18:39, 2 July 2015
Line 1:		Line 1:
			__NOTOC__
	Below are some brief examples of script test modules that use the [[Perl Script APIs]] for STRIDE. Most of these examples are incomplete and are only intended to give a quick overview of how this API can be used.		Below are some brief examples of script test modules that use the [[Perl Script APIs]] for STRIDE. Most of these examples are incomplete and are only intended to give a quick overview of how this API can be used.

Line 221:		Line 222:
	my $value = Remote->SOME_DEFINED_VALUE;		my $value = Remote->SOME_DEFINED_VALUE;
	</source>		</source>

	~~[[Category:Tests in Script]]~~

Ivailop at 23:13, 25 September 2013

2013-09-25T23:13:23Z

← Older revision		Revision as of 23:13, 25 September 2013
Line 6:		Line 6:
	perl -I %STRIDE_DIR%\lib\perl -I %STRIDE_DIR%\lib\perl\5.10 -cw MyTests.pm		perl -I %STRIDE_DIR%\lib\perl -I %STRIDE_DIR%\lib\perl\5.10 -cw MyTests.pm

	* Linux		* Linux/FreeBSD
	perl -I $STRIDE_DIR/lib/perl -I $STRIDE_DIR/lib/perl/5.10 -cw MyTests.pm		perl -I $STRIDE_DIR/lib/perl -I $STRIDE_DIR/lib/perl/5.10 -cw MyTests.pm

Ivailop: /* Reusing a trace data file as expectation */

2011-10-17T20:40:41Z

Reusing a trace data file as expectation

← Older revision		Revision as of 20:40, 17 October 2011
Line 163:		Line 163:
	== Reusing a trace data file as expectation ==		== Reusing a trace data file as expectation ==

	This examples shows a simple way to reuse captured ~~yaml~~ trace data from a file as your expectation (this is an alternative to specifying the <tt>expected</tt> array directly). This example assumes the ''trace_data.~~yaml~~'' file lives in the same directory as the test module file, but you are free to change this - just change the <tt>expect_file</tt> argument accordingly.		This examples shows a simple way to reuse captured YAML trace data from a file as your expectation (this is an alternative to specifying the <tt>expected</tt> array directly). This example assumes the ''trace_data.yml'' file lives in the same directory as the test module file, but you are free to change this - just change the <tt>expect_file</tt> argument accordingly.

	<source lang="perl">		<source lang="perl">
	# these standard modules are only required for the file		# these standard modules are only required for the file
	# path logic used to generate a full file path for trace_data.~~yaml~~		# path logic used to generate a full file path for trace_data.yml
	use File::Basename;		use File::Basename;
	use File::Spec;		use File::Spec;
Line 174:		Line 174:
	my $h = TestPointSetup(		my $h = TestPointSetup(
	ordered => 1,		ordered => 1,
	expect_file => File::Spec->catfile(dirname(__FILE__), 'trace_data.~~yaml~~'),		expect_file => File::Spec->catfile(dirname(__FILE__), 'trace_data.yml'),
	);		);

Ivailop: /* Accessing compiler macro values (constants) */

2011-06-11T05:46:37Z

Accessing compiler macro values (constants)

← Older revision		Revision as of 05:46, 11 June 2011
Line 219:		Line 219:

	<source lang="perl">		<source lang="perl">
	my $value = Remote->{SOME_DEFINED_VALUE};		my $value = Remote->SOME_DEFINED_VALUE;
	</source>		</source>

	[[Category:Tests in Script]]		[[Category:Tests in Script]]

Ivailop: /* Accessing compiler macro values (constants) */

2011-06-11T05:46:19Z

Accessing compiler macro values (constants)

← Older revision		Revision as of 05:46, 11 June 2011
Line 219:		Line 219:

	<source lang="perl">		<source lang="perl">
	my $value = ~~Constants~~->{SOME_DEFINED_VALUE};		my $value = Remote->{SOME_DEFINED_VALUE};
	</source>		</source>

	[[Category:Tests in Script]]		[[Category:Tests in Script]]

Ivailop: /* Invoking a function on the target */

2011-06-11T05:45:24Z

Invoking a function on the target

← Older revision		Revision as of 05:45, 11 June 2011
Line 190:		Line 190:
	<source lang="perl">		<source lang="perl">
	use STRIDE;		use STRIDE;
	$STRIDE::~~Functions~~->MyRemoteFunction();		$STRIDE::Remote->MyRemoteFunction();
	</source>		</source>
	More functions can be added to this script by making additional calls using the $STRIDE::~~Functions~~ object. If your remote function accepts arguments, they should be added to the function call parameters (see the [[Perl_Script_APIs#STRIDE::~~Function~~\|Perl API Reference]] for more information).		More functions can be added to this script by making additional calls using the <tt>$STRIDE::Remote</tt> object. If your remote function accepts arguments, they should be added to the function call parameters (see the [[Perl_Script_APIs#STRIDE::Remote\|Perl API Reference]] for more information).

	=== Making calls with test modules ===		=== Making calls with test modules ===

	Within test modules, remote functions can be easily invoked using the exported ~~Functions~~ object. The following two examples illustrate this.		Within test modules, remote functions can be easily invoked using the exported <tt>Remote</tt> object. The following two examples illustrate this.

	==== Blocking syntax (blocks until function returns) ====		==== Blocking syntax (blocks until function returns) ====

	<source lang="perl">		<source lang="perl">
	my $retval = ~~Functions~~->foo(1, "input string");		my $retval = Remote->foo(1, "input string");
	~~Functions~~->bar();		Remote->bar();
	</source>		</source>

Line 208:		Line 208:

	<source lang="perl">		<source lang="perl">
	my $fh = ~~Functions~~->async->foo(1, "input string");		my $fh = Remote->async->foo(1, "input string");
	my $retval = $fh->Wait(1000); #waits up to one second for the function to return		my $retval = $fh->Wait(1000); #waits up to one second for the function to return
	</source>		</source>