|Note||This command is only available in the Xbase++ dialect|
Provide the implementation for methods that are forward defined between CLASS .. ENDCLASS
[Attributes] [ACCESS | ASSIGN] [Modifiers] METHOD [<ClassName>:] <MethodName>[ [([<idParam> [AS|REF|OUT|IN <idType>] [, ...])] ) [AS <idType>]
|Modifiers||An optional list of one or more modifiers. CLASS, STATIC, ABSTRACT, UNSAFE, ASYNC, EXTERN|
STATIC is a synonym for CLASS.
|Attributes||An 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.|
|ACCESS | ASSIGN||Declares that this method implements a Getter or Setter for a property. This must also be defined as ACCESS or ASSIGN in the class declaration.|
|ClassName||The name of the class in which the class method is declared. When only one class is declared in the PRG file, the class name is optional. Otherwise <ClassName>: is required.|
|<idMethod>||A valid identifier name for the method. Method names must be unique within a class, but can share the same name as other entities (including access and assign methods) 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>||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
|END METHOD||Optional end clause to indicate the end of the inline METHOD entity|
In Xbase++ there are some reserved method names:
|Init||This is the name of the constructor|
|InitClass||This is the name of the class constructor.|
The implementation of constructors in .Net is somewhat different from Xbase++.
•Therefore the class constructor cannot have any parameters.
•The parameters of the Init() method become the constructor parameters.