Scripting: Do's and Don'ts – Arma Reforger

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "</syntaxhighlight>" to "</enforce>")
m (Some wiki formatting)
Line 1: Line 1:
{{Feature|important|Follow [[Arma Reforger:Scripting: Conventions]].}}
{| class="wikitable" style="width: 100%"
{| class="wikitable" style="width: 100%"
|+ {{Feature|important|Do follow {{Link|Arma Reforger:Scripting: Conventions|Scripting Conventions}}.}}
! style="width: 50%" | Don't
! style="width: 50%" | Don't
! style="width: 50%" | Do
! style="width: 50%" | Do
|- style="vertical-align: top"
|- style="vertical-align: top"
|
|
<enforce>
<enforce noGuess>
class ExampleClass {
class ExampleClass {
   int LProcLgh;
   int LProcLgh;
Line 38: Line 37:
|}
|}


Keep variables as close as possible to their usage:
{| class="wikitable" style="width: 100%"
{| class="wikitable" style="width: 100%"
|+ {{Feature|important|Keep variables as close as possible to their usage.}}
! style="width: 50%" | Don't
! style="width: 50%" | Don't
! style="width: 50%" | Do
! style="width: 50%" | Do
Line 73: Line 72:
|}
|}


Keep a strong reference ({{hl|ref}} keyword) to required objects:
{| class="wikitable" style="width: 100%"
{| class="wikitable" style="width: 100%"
|+ {{Feature|important|Keep a strong reference (<enforce inline>ref</enforce> keyword) to required objects.}}
! style="width: 50%" | Don't
! style="width: 50%" | Don't
! style="width: 50%" | Do
! style="width: 50%" | Do
Line 105: Line 104:
|}
|}


Avoid strong reference cyclic trap:
{| class="wikitable" style="width: 100%"
{| class="wikitable" style="width: 100%"
|+ {{Feature|important|Avoid strong reference cyclic trap.}}
! style="width: 50%" | Don't
! style="width: 50%" | Don't
! style="width: 50%" | Do
! style="width: 50%" | Do
Line 114: Line 113:
class MainClass
class MainClass
{
{
ref SubClass m_subClass;
ref SubClass m_SubClass;
   
   
void MainClass()
void MainClass()
{
{
m_subClass = new SubClass(this);
m_SubClass = new SubClass(this);
}
}
}
}
Line 124: Line 123:
class SubClass
class SubClass
{
{
ref MainClass m_parent;
ref MainClass m_Parent;
   
   
void SubClass(MainClass parent)
void SubClass(MainClass parent)
{
{
m_parent = parent;
m_Parent = parent;
}
}
   
   
void DoSomething()
void DoSomething()
{
{
Print(m_parent);
Print(m_Parent);
}
}
}
}
Line 141: Line 140:
class MainClass
class MainClass
{
{
ref SubClass m_subClass;
ref SubClass m_SubClass;
   
   
void MainClass()
void MainClass()
{
{
m_subClass = new SubClass(this);
m_SubClass = new SubClass(this);
}
}
}
}
Line 151: Line 150:
class SubClass
class SubClass
{
{
MainClass m_parent; // ref removed
MainClass m_Parent; // ref removed
   
   
void SubClass(MainClass parent)
void SubClass(MainClass parent)
{
{
m_parent = parent;
m_Parent = parent;
}
}
   
   
void DoSomething()
void DoSomething()
{
{
if (!m_parent) // null safety check
if (!m_Parent) // null safety check
{
return;
return;
}
 
Print(m_parent);
Print(m_Parent);
}
}
}
}

Revision as of 01:11, 17 June 2023

Don't Do

class ExampleClass { int LProcLgh; int stringlength( string Value ){ LProcLgh= Value.Length(); Print ( "String length obtained: "+LProcLgh ); return LProcLgh; } }

class ExampleClass { protected int m_iLastProcessedLength; int GetStringLength(string value) { m_iLastProcessedLength = value.Length(); Print("String length obtained: " + m_iLastProcessedLength); return m_iLastProcessedLength; } int GetLastProcessedLength() { return m_iLastProcessedLength; } }

Keep variables as close as possible to their usage.
Don't Do

class ExampleClass { protected int m_iLength; int GetStringLength(string name) { m_iLength = name.Length(); Print("String length obtained: " + m_iLength); return m_iLength; } }

class ExampleClass { // keeping the variable into method scope and away from the instance int GetStringLength(string name) { int length = name.Length(); Print("String length obtained: " + length); return length; } }

Keep a strong reference (ref keyword) to required objects.
Don't Do

// this array only lists pointers but does not increase the reference count array<ExampleClass> classArray = new array<ExampleClass>(); for (int i = 0; i < 10; i++) { ExampleClass newInstance = new ExampleClass(); classArray.Insert(newInstance); // newInstance will be deleted at the end of the scope // as there are no references to it }

// this array keeps strong references to its items array<ref ExampleClass> classArray = new array<ref ExampleClass>(); for (int i = 0; i < 10; i++) { ExampleClass newInstance = new ExampleClass(); classArray.Insert(newInstance); // classArray keeps a strong reference to newInstance - it will not be cleared }

Avoid strong reference cyclic trap.
Don't Do
Here, both ParentClass and ChildClass have a strong reference to each other, keeping the reference count above zero - creating an "island of isolation" (see Arma Reforger:Scripting: Automatic Reference Counting for more information).

class MainClass { ref SubClass m_SubClass; void MainClass() { m_SubClass = new SubClass(this); } } class SubClass { ref MainClass m_Parent; void SubClass(MainClass parent) { m_Parent = parent; } void DoSomething() { Print(m_Parent); } }

Here, the MainClass needs the SubClass (it creates it in its constructor meaning it needs it to work) but the subClass does not require MainClass - if the MainClass reference doesn't exist, it will simply not use it.

class MainClass { ref SubClass m_SubClass; void MainClass() { m_SubClass = new SubClass(this); } } class SubClass { MainClass m_Parent; // ref removed void SubClass(MainClass parent) { m_Parent = parent; } void DoSomething() { if (!m_Parent) // null safety check return; Print(m_Parent); } }