Show/Hide Toolbars

XSharp

Purpose

Declare a method to access a non-exported or virtual instance variable.

Syntax

 [Attributes] [Modifiers] PROPERTY<idName>

 [([<idParam> [AS | REF <idType>] [, ...])]

 [AS <idType>] [<idConvention>]
 [

        AUTO [Attributes] [Modifiers] GET | SET | INIT

             | [  [Attributes] [Modifiers] GET <Expression> ]  [ [Attributes] [Modifiers] SET <Expression>]   [ [Attributes] [Modifiers] INIT <Expression>]  

 CRLF

             | [  [Attributes] [Modifiers] GET <Body > END GET]

             | [  [Attributes] [Modifiers] GET => <Expression>]

             | [ [Attributes] [Modifiers]  SET <Body > END SET]

             | [  [Attributes] [Modifiers] SET => <Expression>]

             | [ [Attributes] [Modifiers]  INIT <Body > END INIT]

             | [  [Attributes] [Modifiers] INIT => <Expression>]

   END PROPERTY

             ]

Arguments

AttributesAn optional list of one or more attributes that describe meta information for am entity, such as for example the [TestMethod] attribute on a method/function containing tests in a MsTest class library. Please note that Attributes must be on the same line or suffixed with a semi colon when they are written on the line above that keyword.

 

<idName>A valid identifier name for the property that you are defining.  Like other methods, properties are entities. Property names must be unique within a class, but can share the same name as other entities in your application.

 

<idParam>A  parameter variable.  A variable specified in this manner is automatically declared local.  These variables, also called formal parameters, are used to receive arguments that you pass when you call the entity.

 

AS | REF|OUT|IN <idType>Specifies the data type of the parameter variable (called strong typing).  AS indicates that the parameter must be passed by value, and REF indicates that it must be passed by reference with the @ operator. OUT is a special kind of REF parameter that does not have to be assigned before the call and must be assigned inside the body of the entity. IN parameters are passed as READONLY references.
The last parameter in the list can also be declared as PARAMS <idType>[] which will tell the compiler that the function/method may receive zero or more optional parameters.
Functions or Methods of the CLIPPER calling convention are compiled to a function with a single parameter that this declared as Args PARAMS USUAL[]
 

 

AS <idType>Specifies the data type.  If omitted, then depending on the compiler options the type will be either USUAL or determined by the compiler.

 

<Expression>Expression that implements the accessor

 

=> <Expression>Single expression that replaces the multiline body for the entity. CANNOT be compiled with a body

 

<Body>Program statements that form the code of this entity.
The <Body> can contain one or more RETURN statements to return control to the calling routine and to serve as the function return value.  If no return statement is specified, control passes back to the calling routine when the function definition ends, and the function will return a default value depending on the return value data type specified (NIL if the return value is not strongly typed).
CANNOT be combined with an Expression Body

 

Description

There are 3 types of property declarations:

Single line declaration without AUTO clause

Single line declaration with GET / SET / INIT accessors

Multi line declaration with GET accessor block and/or SET/INIT accessor bock. For multi line declarations the END PROPERTY is mandatory

 

INIT accessor declare that a property can only be changed in the constructor of a class. A property cannot have both a SET and an INIT accessor.

 

See Also

ASSIGN, CLASS, METHOD