There is no spoon
Difference between revisions of "Compiler issues"
From Unreal Wiki, The Unreal Engine Documentation Site
m (→Parsing Issues: Fixed format) |
m (→Parsing Issues: Swapped ...) |
||
Line 20: | Line 20: | ||
{{CorrectWrong|<uscript> | {{CorrectWrong|<uscript> | ||
− | |||
− | |||
defaultproperties | defaultproperties | ||
{ | { | ||
+ | }</uscript>|<uscript> | ||
+ | defaultproperties{ | ||
}</uscript>}} | }</uscript>}} |
Revision as of 01:20, 23 September 2010
Like any other compiler there are issues with the parsing therefor this page exists to mention those common issues and how to get around them.
Parsing Issues
Comment Issues related to the comments
- Having an end of multi-line comment proceeded by a line comment on the same line.
Correct and Wrong example
Correct |
Wrong |
/* if(!bUseForVehicles)
return Super.DamageTaken(Enemy, Injured);
else{//Branch4: Do vehicle code here, optimized?}
*/ /*local int LogInitHealth;*/ /*, LogDamage, LogConversion;*/ |
/* if(!bUseForVehicles)
return Super.DamageTaken(Enemy, Injured);
else{//Branch4: Do vehicle code here, optimized?}*/ /*local int LogInitHealth;*//*, LogDamage, LogConversion;*/ |
DefaultProperties Issues related to the defaultproperties block
- Placing a { on the same line of the defaultproperties declaration will cause the parser to skip the defaultproperties block thus :all of your default values will not be compiled, to get around this is easy just place the { on the next line!.
Correct and Wrong example
Correct |
Wrong |
defaultproperties { } |
defaultproperties{ } |