Studio:Scl ptr sized - Revision history

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

2009-08-21T00:41:50Z

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

← Older revision		Revision as of 00:41, 21 August 2009
Line 118:		Line 118:
	For additional information on scl_ptr_sized, including constraints, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].		For additional information on scl_ptr_sized, including constraints, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].

	[[Category: Pointers]]		[[Category:Studio:Pointers]]
	[[Category:Studio:SCL]]		[[Category:Studio:SCL]]

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

2009-08-21T00:11:51Z

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

← Older revision		Revision as of 00:11, 21 August 2009
Line 119:		Line 119:

	[[Category: Pointers]]		[[Category: Pointers]]
	[[Category: SCL]]		[[Category:Studio:SCL]]

Timd: Scl ptr sized moved to Studio:Scl ptr sized

2009-08-18T22:40:26Z

Scl ptr sized moved to Studio:Scl ptr sized

← Older revision	Revision as of 22:40, 18 August 2009
(No difference)

Robg: /* Error Conditions */

2008-10-09T22:21:13Z

Error Conditions

← Older revision		Revision as of 22:21, 9 October 2008
Line 86:		Line 86:

	== Error Conditions ==		== Error Conditions ==
	* A compiler error will be reported if ~~an embedded~~ pointer does not point to a fixed size type.		* A compiler error will be reported if a pointer does not point to a fixed size type.
	* Sized pointers cannot use the "INOUT" direction.		* Sized pointers cannot use the "INOUT" direction.
	* Response payloads cannot use the "OUT" or "INOUT" direction.		* Response payloads cannot use the "OUT" or "INOUT" direction.

Robg: /* Notes */

2008-10-09T22:20:51Z

Notes

← Older revision		Revision as of 22:20, 9 October 2008
Line 81:		Line 81:
	:# Fixed-sized always points to the same number of elements as specified by max-size.		:# Fixed-sized always points to the same number of elements as specified by max-size.
	:# Variable-sized points to a variable number of elements. The number of elements currently pointed to is indicated by size-field-name, which must be of type integer.		:# Variable-sized points to a variable number of elements. The number of elements currently pointed to is indicated by size-field-name, which must be of type integer.
	* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single ~~embedded~~ pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.		* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.
	* ~~Currently, the~~ type of the ~~data that is pointed to~~ cannot be void; ~~for example,~~ void *. This is considered an opaque pointer.		* The type of the pointer cannot be pointer to void; e.g. void *. This is considered an opaque pointer.
	* As of STRIDE 3.0.0102 the direction and usage attributes are not symbolic tokens anymore. They became string literals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.		* As of STRIDE 3.0.0102 the direction and usage attributes are not symbolic tokens anymore. They became string literals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.

Stevel: /* See Also */

2008-10-08T20:34:32Z

Ivailop: /* Notes */

2008-10-07T21:02:06Z

Notes

← Older revision		Revision as of 21:02, 7 October 2008
Line 83:		Line 83:
	* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.		* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.
	* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.
	* As of STRIDE 3.0.0102 the direction and usage attributes are not tokens anymore. They became string literals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.		* As of STRIDE 3.0.0102 the direction and usage attributes are not symbolic tokens anymore. They became string literals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.

	== Error Conditions ==		== Error Conditions ==

Ivailop: /* Notes */

2008-10-07T20:43:48Z

Notes

← Older revision		Revision as of 20:43, 7 October 2008
Line 83:		Line 83:
	* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.		* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.
	* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.
	* As of STRIDE 3.0.0102 the direction and usage attributes are not tokens anymore. They ~~become~~ string ~~litarals~~ (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.		* As of STRIDE 3.0.0102 the direction and usage attributes are not tokens anymore. They became string literals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.

	== Error Conditions ==		== Error Conditions ==

Ivailop: /* Notes */

2008-10-07T20:43:22Z

Notes

← Older revision		Revision as of 20:43, 7 October 2008
Line 83:		Line 83:
	* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.		* If the sized pointer is "IN", then size-field-name can be a non-pointer integer type; otherwise it must be a single embedded pointer. In either case, the parameter size-field-name must have the same direction as its associated-sized pointer.
	* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; for example, void *. This is considered an opaque pointer.
			* As of STRIDE 3.0.0102 the direction and usage attributes are not tokens anymore. They become string litarals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.

	== Error Conditions ==		== Error Conditions ==

Ivailop: /* Syntax */

2008-10-07T20:19:58Z

Syntax

← Older revision		Revision as of 20:19, 7 October 2008
Line 4:		Line 4:

	== Syntax ==		== Syntax ==
	#pragma scl_ptr_sized(type-name, direction, ~~pointer-~~usage, max-size)		#pragma scl_ptr_sized(type-name, direction, usage, max-size)

	#pragma scl_ptr_sized(type-name, direction, ~~pointer-~~usage, max-size, size-field-name)		#pragma scl_ptr_sized(type-name, direction, usage, max-size, size-field-name)

	#pragma scl_ptr_sized(type-name, field-name, direction, ~~pointer-~~usage, max-size)		#pragma scl_ptr_sized(type-name, field-name, direction, usage, max-size)

	#pragma scl_ptr_sized(type-name, field-name, direction, ~~pointer-~~usage, max-size, size-field-name)		#pragma scl_ptr_sized(type-name, field-name, direction, usage, max-size, size-field-name)

	{\| border="1" cellspacing="0" cellpadding="10" style="align:left;"		{\| border="1" cellspacing="0" cellpadding="10" style="align:left;"
Line 26:		Line 26:
	\|-		\|-
	\| ''direction''		\| ''direction''
	\| ~~Constant~~		\| String
	\| Direction in which the pointer data is marshaled; refer to the Pointer Direction Table below. This affects read and write access to the pointer data.		\| Direction in which the pointer data is marshaled; refer to the Pointer Direction Table below. This affects read and write access to the pointer data.
	\|-		\|-
	\| ''~~pointer-~~usage''		\| ''usage''
	\| ~~Constant~~		\| String
	\| Pointer usage indicator; refer to the Pointer Memory Usage Table below.		\| Pointer usage indicator; refer to the Pointer Memory Usage Table below.
	\|-		\|-

← Older revision		Revision as of 20:34, 8 October 2008
Line 116:		Line 116:

	== See Also ==		== See Also ==
	For additional information on scl_ptr_sized, including constraints, refer to the [~~http~~:~~//www.s2technologies.com/pdf/~~s2sSCLReferenceGuide.pdf SCL Reference Guide].		For additional information on scl_ptr_sized, including constraints, refer to the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].

	[[Category: Pointers]]		[[Category: Pointers]]
	[[Category: SCL]]		[[Category: SCL]]