My program doesn't have bugs. It just develops random features.
Difference between revisions of "Import"
From Unreal Wiki, The Unreal Engine Documentation Site
(New page for the keyword "Import", does anybody else know about this? This seems to compile and have an affect on the data in the compiled .u files, but the practical uses seems questionable!) |
(No difference)
|
Latest revision as of 14:03, 27 February 2014
The UnrealScript keyword "Import" provides a way to define imports at the classes' scope. This keyword is officially undocumented and nowhere used by Epic Games, although it is available and compilable in the Unreal Engine 1 and 2. The keyword has been used by some licensees of the Unreal Engine.
Syntax[edit]
The import syntax looks like this:
import package|enum|struct|class type [from package];
Importing packages[edit]
import package Engine;
Note: Works but the purpose of this is unknown.
Importing enums[edit]
import enum EDrawType from Engine;
Note: Crashes the the compiler, maybe wrong code?
Example[edit]
A complete example:
class MyActor extends Actor; import package Engine;
| Declarations | Preprocessor • Classes • Interfaces • Cpptext • Constants • Enums • Structs • Variables (Metadata) • Replication block • Operators • Delegates • Functions • States • Defaultproperties (Subobjects) |
|---|---|
| Types | bool • byte • float • int • name • string • Object • Class • Enums • Structs (Vector ⋅ Rotator ⋅ Quat ⋅ Color) • Static arrays • Dynamic arrays • Delegates • Typecasting |
| Literals | Boolean • Float • Integer • Names • Objects (None ⋅ Self) • Vectors • Rotators • Strings |
| Flow | GoTo • If • Assert • Return • Stop • Switch • While • Do...Until • For • ForEach • Break • Continue |
| Specifiers | Super • Global • Static • Default • Const |
| UnrealScript | Syntax • .UC • .UCI • .UPKG • Comments • #directives • Native |
