Studio:SCL Pragmas - Revision history

Timd: Text replace - 'Category: Reference' to 'Category:Studio:Reference'

2009-08-21T15:56:41Z

Text replace - 'Category: Reference' to 'Category:Studio:Reference'

← Older revision		Revision as of 15:56, 21 August 2009
Line 136:		Line 136:

	[[Category:Studio:SCL]]		[[Category:Studio:SCL]]
	[[Category: Reference]]		[[Category:Studio:Reference]]

Timd: Text replace - 'Category: SCL' to 'Category:Studio:SCL'

2009-08-21T00:10:07Z

Text replace - 'Category: SCL' to 'Category:Studio:SCL'

← Older revision		Revision as of 00:10, 21 August 2009
Line 135:		Line 135:
	*Refer to the '''SCL Wizard''' section of the STRIDE Online Help for information on how to create SCL pragmas.		*Refer to the '''SCL Wizard''' section of the STRIDE Online Help for information on how to create SCL pragmas.

	[[Category: SCL]]		[[Category:Studio:SCL]]
	[[Category: Reference]]		[[Category: Reference]]

Timd: SCL Pragmas moved to Studio:SCL Pragmas

2009-08-18T21:34:07Z

SCL Pragmas moved to Studio:SCL Pragmas

← Older revision	Revision as of 21:34, 18 August 2009
(No difference)

Timd at 18:27, 10 June 2009

2009-06-10T18:27:51Z

← Older revision		Revision as of 18:27, 10 June 2009
Line 75:		Line 75:
	The SCL pragmas are listed here, categorized by function:		The SCL pragmas are listed here, categorized by function:

	=== Test Units ===		=== [[Test Unit Pragmas\|Test Units]] ===

	* [[scl_test_class]]		* [[scl_test_class]]

Robg: /* Qualification */

2008-11-05T18:03:03Z

Qualification

← Older revision		Revision as of 18:03, 5 November 2008
Line 100:		Line 100:
	* [[scl_ptr_sized]]		* [[scl_ptr_sized]]
	* [[scl_string]]		* [[scl_string]]
	* [[scl_struct_sized]] ~~''(coming soon)''~~		* [[scl_struct_sized]]
	* [[scl_union]]		* [[scl_union]]
	* [[scl_union_activate]]		* [[scl_union_activate]]

Robg: /* Message Payloads */

2008-11-05T17:53:59Z

Message Payloads

← Older revision		Revision as of 17:53, 5 November 2008
Line 49:		Line 49:


	Note that in this instance, the payload actually consists of two distinct memory blocks ~~&endash;~~ a pointer and the structure pointed to. The distinct blocks in a payload are referred to as the payload blocks. Note also that the blocks form a tree structure, with each contiguous memory block representing a node in the tree. This illustrates a more general concept: the payload blocks form a network, and that network must be a tree (i.e., it starts with a node designated as the root, and all other nodes are reachable from the root. There cannot be cycles).		Note that in this instance, the payload actually consists of two distinct memory blocks, a pointer and the structure pointed to. The distinct blocks in a payload are referred to as the payload blocks. Note also that the blocks form a tree structure, with each contiguous memory block representing a node in the tree. This illustrates a more general concept: the payload blocks form a network, and that network must be a tree (i.e., it starts with a node designated as the root, and all other nodes are reachable from the root. There cannot be cycles).

	Within a two-way message, the structure of data passed in each direction may be different. For this reason, payloads must be further defined according to whether they are passed from user to owner or owner to user. Payloads passed from user to owner are called Command Payloads. Payloads passed from owner to user are called Response Payloads.		Within a two-way message, the structure of data passed in each direction may be different. For this reason, payloads must be further defined according to whether they are passed from user to owner or owner to user. Payloads passed from user to owner are called Command Payloads. Payloads passed from owner to user are called Response Payloads.

Chrisj: /* Qualification */

2008-11-01T00:08:36Z

Qualification

← Older revision		Revision as of 00:08, 1 November 2008
Line 98:		Line 98:
	* [[scl_ptr_flist]]		* [[scl_ptr_flist]]
	* [[scl_ptr_opaque]]		* [[scl_ptr_opaque]]
	* [[scl_ptr_sized]] ~~''(coming soon)''~~		* [[scl_ptr_sized]]
	* [[scl_string]]		* [[scl_string]]
	* [[scl_struct_sized]]		* [[scl_struct_sized]] ''(coming soon)''
	* [[scl_union]]		* [[scl_union]]
	* [[scl_union_activate]]		* [[scl_union_activate]]

Chrisj: /* Qualification */

2008-11-01T00:08:14Z

Qualification

← Older revision		Revision as of 00:08, 1 November 2008
Line 98:		Line 98:
	* [[scl_ptr_flist]]		* [[scl_ptr_flist]]
	* [[scl_ptr_opaque]]		* [[scl_ptr_opaque]]
	* [[scl_ptr_sized]]		* [[scl_ptr_sized]] ''(coming soon)''
	* [[scl_string]]		* [[scl_string]]
	* [[scl_struct_sized]]		* [[scl_struct_sized]]

Chrisj: /* Qualification */

2008-10-31T23:45:13Z

Qualification

← Older revision		Revision as of 23:45, 31 October 2008
Line 100:		Line 100:
	* [[scl_ptr_sized]]		* [[scl_ptr_sized]]
	* [[scl_string]]		* [[scl_string]]
			* [[scl_struct_sized]]
	* [[scl_union]]		* [[scl_union]]
	* [[scl_union_activate]]		* [[scl_union_activate]]

Ivailop: /* Notes */

2008-10-17T19:03:01Z

Notes

← Older revision		Revision as of 19:03, 17 October 2008
Line 122:		Line 122:

	* The use of packed pragmas may result in structure alignment issues when communicating with the target platform.		* The use of packed pragmas may result in structure alignment issues when communicating with the target platform.

			* STRIDE pragmas should be added to header (.h) files. Although such pragmas could be added to implementation (.c/cpp) files it is not recommended because it may lead to linkage problems when integrating the generated IM code in to your application.

	== See Also ==		== See Also ==