The __declspec Keyword Extension
Some arguments to the __declspec keyword extension provide language support for the libraries. These arguments are listed below. Macros for the declspec arguments and combinations of them are defined in sysmac.h. In most cases you do not need to specify these. When you do need to add them, you should use the macros.
The delphiclass argument is used for declarations of classes derived from TObject. These classes are created with the following compatibility:
- Object Pascal-compatible RTTI
- Library-compatible constructor/destructor behavior
- Library-compatible exception handling
A library-compatible class has the following restrictions:
- No virtual base classes are allowed.
- No multiple inheritance is allowed except for the case described in Inheritance and Interfaces.
- Must be dynamically allocated by using the global new operator.
Note: In case an instance is statically allocated (for example, as a local variable), the compiler simply ignores the declspec directive, with no warning.
- Must have a destructor.
- Copy constructors and assignment operators are not compiler-generated for library-derived classes.
- A class declaration that is translated from Object Pascal needs this modifier if the compiler needs to know that the class is derived from TObject.
The delphirecord storage class attribute is used when converting Object Pascal records into C++ classes/structs in .hpp headers (using the Object Pascal compiler). In Object Pascal there is a convention regarding records being returned from functions, which states that a function returning a record returns a hidden parameter pointing to the record to be returned. Object Pascal returns a pointer to a location that is zero initialized, whereas C++ does not offer such a guarantee. For compliance, when C++ finds a struct that is being returned from a function and is flagged as __declspec(delphirecord), it zeroes out the memory location.
The delphireturn argument is for internal use only by the libraries in Appmethod C++. It is used for declarations of classes that were created in Appmethod C++ to support Object Pascal built-in data types and language constructs, because they do not have a native C++ type. These include Currency, UnicodeString, AnsiString, Variant, TDateTime, and Set. The delphireturn argument marks C++ classes for library-compatible handling in function calls as parameters and return values. This modifier is needed when passing a structure by value to a function between Object Pascal and C++.
The delphirtti argument causes the compiler to include runtime type information in a class when it is compiled. When this modifier is used, the compiler generates runtime type information for all fields, methods, and properties that are declared in a published section. For interfaces, the compiler generates runtime type information for all methods of the interface. If a class is compiled with runtime type information, all of its descendants also include runtime type information. Because the TPersistent class is compiled with runtime type information, this means that there is no need to use this modifier with any classes you create that have TPersistent as an ancestor. This modifier is primarily used for interfaces in applications that implement or use Web Services.
The dynamic argument is used for declarations of dynamic functions. Dynamic functions are similar to virtual functions except that they are stored only in the vtables for the objects that define them, not in descendent vtables. If you call a dynamic function, and that function is not defined in your object, the vtables of its ancestors are searched until the function is found. Dynamic functions are only valid for classes derived from TObject.
The hidesbase argument preserves Object Pascal program semantics when porting Object Pascal virtual and override functions to Appmethod C++. In Object Pascal, virtual functions in base classes can appear in the derived class as a function of the same name, but which is intended to be a completely new function with no explicit relation to the earlier one.
The compilers use the HIDESBASE macro, defined in sysmac.h, to specify that these types of function declarations are completely separate. For example, if a base class, T1, declares a virtual function, func, taking no arguments, and its derived class, T2, declared a function with the same name and signature, the Object Pascal compiler would produce an HPP file with the following prototype:
virtual void T1::func(void) ; HIDESBASE void T2::func(void) ;
Without the HIDESBASE declaration, the C++ program semantics indicate that virtual function T1::func() is being overridden by T2::func().
The package argument indicates that the code defining the class can be compiled in a package. This modifier is auto-generated by the compiler when creating packages in the IDE.
The pascalimplementation argument indicates that the code defining the class was implemented in Object Pascal. This modifier appears in an Object Pascal portability header file with an .hpp extension.
The uuid argument associates a class with a globally unique identifier (GUID). This can be used with any class, but is typically used with classes that represent Object Pascal interfaces (or COM interfaces). You can retrieve the GUID of a class that was declared using this modifier by calling the __uuidof directive.