Studio:Scl ptr - Revision history

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

2009-08-21T00:41:37Z

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

← Older revision		Revision as of 00:41, 21 August 2009
Line 114:		Line 114:
	</source>		</source>

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

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

2009-08-21T00:10:55Z

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

← Older revision		Revision as of 00:10, 21 August 2009
Line 115:		Line 115:

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

Timd: Scl ptr moved to Studio:Scl ptr

2009-08-18T22:41:51Z

Scl ptr moved to Studio:Scl ptr

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

Robg: /* Notes */

2008-10-09T22:11:51Z

Notes

← Older revision		Revision as of 22:11, 9 October 2008
Line 65:		Line 65:
	== Notes ==		== Notes ==
	* A compiler error will be reported if an pointer does not point to a fixed size type.		* A compiler error will be reported if an pointer does not point to a fixed size type.
	* 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.
	* Pointers with "OUT" or "INOUT" direction cannot indicate POOL pointer usage.		* Pointers with "OUT" or "INOUT" direction cannot indicate POOL pointer usage.
	* 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.
	* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.		* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.
	* ~~Currently, the~~ type ~~of the data that is pointed to~~ cannot be void; e.g., void *. This is considered an opaque pointer.		* The pointers declared type cannot be pointer to void; e.g., void *. This is considered an opaque pointer.
	* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].		* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].
	* 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.

Robg: /* Notes */

2008-10-09T22:07:43Z

Notes

← Older revision		Revision as of 22:07, 9 October 2008
Line 68:		Line 68:
	* Response payloads cannot use the "OUT" or "INOUT" direction.		* Response payloads cannot use the "OUT" or "INOUT" direction.
	* Pointers with "OUT" or "INOUT" direction cannot indicate POOL pointer usage.		* Pointers with "OUT" or "INOUT" direction cannot indicate POOL pointer usage.
	* 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.
	* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.		* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.
	* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.

Robg: /* Notes */

2008-10-09T22:06:54Z

Notes

← Older revision		Revision as of 22:06, 9 October 2008
Line 64:		Line 64:

	== Notes ==		== Notes ==
	* 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 an 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.

Stevel at 20:06, 8 October 2008

2008-10-08T20:06:43Z

← Older revision		Revision as of 20:06, 8 October 2008
Line 71:		Line 71:
	* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.		* One-way messages (command and response) cannot have data that contains an "OUT" or "INOUT" Pointer.
	* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.
	* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [~~http~~:~~//www.s2technologies.com/pdf/~~s2sSCLReferenceGuide.pdf SCL Reference Guide].		* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [[Media:s2sSCLReferenceGuide.pdf\|SCL Reference Guide]].
	* 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.

Ivailop: /* Notes */

2008-10-07T21:01:33Z

Notes

← Older revision		Revision as of 21:01, 7 October 2008
Line 72:		Line 72:
	* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.
	* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].		* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].
	* 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.

	== Examples ==		== Examples ==

Ivailop: /* Notes */

2008-10-07T20:44:59Z

Notes

← Older revision		Revision as of 20:44, 7 October 2008
Line 72:		Line 72:
	* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.
	* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].		* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].
	* 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.

	== Examples ==		== Examples ==

Ivailop: /* Notes */

2008-10-07T20:42:05Z

Notes

← Older revision		Revision as of 20:42, 7 October 2008
Line 72:		Line 72:
	* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.		* Currently, the type of the data that is pointed to cannot be void; e.g., void *. This is considered an opaque pointer.
	* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].		* For additional information on scl_ptr, including constraints, refer to the section on scl_ptr in the [http://www.s2technologies.com/pdf/s2sSCLReferenceGuide.pdf SCL Reference Guide].
	* As of STRIDE 3.0.0102 the direction and usage attributes are string litarals. ~~See this [[~~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 become string litarals (need to be quoted). See this [[Handling_of_pointer_attribute_tokens\|page]] for details.

	== Examples ==		== Examples ==