Chapter 1.12: What Does NOT Exist (Gotchas)

Home | << Previous: Error Handling | Gotchas | Next: Functions & Methods >>

---

Spis tresci

• Complete Gotchas Reference
  1. No Ternary Operator
  2. No do...while Loop
  3. No try/catch/throw
  4. No Multiple Inheritance
  5. No Operator Overloading (Except Index)
  6. No Lambdas / Anonymous Functions
  7. No Delegates / Function Pointers (Native)
  8. No String Escape for Backslash/Quote
  9. No Variable Redeclaration in else-if Blocks
  10. No Ternary in Variable Declaration
  11. Object.IsAlive() Does NOT Exist on Base Object
  12. No nullptr — Use NULL or null
  13. switch/case Does NOT Fall Through
  14. No Default Parameter Expressions
  15. JsonFileLoader.JsonLoadFile Returns void
  16. No #define Value Substitution
  17. No Interfaces / Abstract Classes (Enforced)
  18. No Generics Constraints
  19. No Enum Validation
  20. No Variadic Parameters
  21. No Nested Class Declarations
  22. Static Arrays Are Fixed-Size
  23. array.Remove Is Unordered
  24. No #include — Everything via config.cpp
  25. No Namespaces
  26. String Methods Modify In-Place
  27. ref Cycles Cause Memory Leaks
  28. No Destructor Guarantee on Server Shutdown
  29. No Scope-Based Resource Management (RAII)
  30. GetGame().GetPlayer() Returns null on Server
  31. sealed Classes Cannot Be Extended (1.28+)
  32. Method Parameter Limit: 16 Maximum (1.28+)
  33. Obsolete Attribute Warnings (1.28+)
  34. int.MIN Comparison Bug
  35. Array Element Boolean Negation Fails
  36. Complex Expression in Array Assignment Crashes
  37. foreach on Method Return Value Crashes
  38. Bitwise vs Comparison Operator Precedence
  39. Empty #ifdef / #ifndef Blocks Crash
  40. GetGame().IsClient() Returns False During Load
  41. Compile Error Messages Report Wrong File
  42. crash_*.log Files Are Not Crashes
• Coming From C++
• Coming From C#
• Coming From Java
• Coming From Python
• Quick Reference Table
• Navigation

---

Complete Gotchas Reference

1. No Ternary Operator

What you would write:

int x = (condition) ? valueA : valueB;

What happens: Compile error. The ? : operator does not exist.

Correct solution:

int x;
if (condition)
    x = valueA;
else
    x = valueB;

---

2. No do...while Loop

What you would write:

do {
    Process();
} while (HasMore());

What happens: Compile error. The do keyword does not exist.

Correct solution — flag pattern:

bool first = true;
while (first || HasMore())
{
    first = false;
    Process();
}

Correct solution — break pattern:

while (true)
{
    Process();
    if (!HasMore())
        break;
}

---

3. No try/catch/throw

What you would write:

try {
    RiskyOperation();
} catch (Exception e) {
    HandleError(e);
}

What happens: Compile error. These keywords do not exist.

Correct solution: Guard clauses with early return.

void DoOperation()
{
    if (!CanDoOperation())
    {
        ErrorEx("Cannot perform operation", ErrorExSeverity.WARNING);
        return;
    }

    // Proceed safely
    RiskyOperation();
}

See Chapter 1.11 — Error Handling for full patterns.

---

4. No Multiple Inheritance

What you would write:

class MyClass extends BaseA, BaseB  // Two base classes

What happens: Compile error. Only single inheritance is supported.

Correct solution: Inherit from one class, compose the other:

class MyClass extends BaseA
{
    ref BaseB m_Helper;

    void MyClass()
    {
        m_Helper = new BaseB();
    }
}

---

5. No Operator Overloading (Except Index)

What you would write:

Vector3 operator+(Vector3 a, Vector3 b) { ... }
bool operator==(MyClass other) { ... }

What happens: Compile error. Custom operators cannot be defined.

Correct solution: Use named methods:

class MyVector
{
    float x, y, z;

    MyVector Add(MyVector other)
    {
        MyVector result = new MyVector();
        result.x = x + other.x;
        result.y = y + other.y;
        result.z = z + other.z;
        return result;
    }

    bool Equals(MyVector other)
    {
        return (x == other.x && y == other.y && z == other.z);
    }
}

Exception: The index operator [] can be overloaded via Get(index) and Set(index, value) methods:

class MyContainer
{
    int data[10];

    int Get(int index) { return data[index]; }
    void Set(int index, int value) { data[index] = value; }
}

MyContainer c = new MyContainer();
c[3] = 42;        // Calls Set(3, 42)
int v = c[3];     // Calls Get(3)

---

6. No Lambdas / Anonymous Functions

What you would write:

array.Sort((a, b) => a.name.CompareTo(b.name));
button.OnClick += () => { DoSomething(); };

What happens: Compile error. Lambda syntax does not exist.

Correct solution: Define named methods and pass them as ScriptCaller or use string-based callbacks:

// Named method
void OnButtonClick()
{
    DoSomething();
}

// String-based callback (used by CallLater, timers, etc.)
GetGame().GetCallQueue(CALL_CATEGORY_GAMEPLAY).CallLater(this.OnButtonClick, 1000, false);

---

7. No Delegates / Function Pointers (Native)

What you would write:

delegate void MyCallback(int value);
MyCallback cb = SomeFunction;
cb(42);

What happens: Compile error. The delegate keyword does not exist.

Correct solution: Use ScriptCaller, ScriptInvoker, or string-based method names:

// ScriptCaller (single callback)
ScriptCaller caller = ScriptCaller.Create(MyFunction);

// ScriptInvoker (event with multiple subscribers)
ref ScriptInvoker m_OnEvent = new ScriptInvoker();
m_OnEvent.Insert(MyHandler);
m_OnEvent.Invoke();  // Calls all registered handlers

---

8. No String Escape for Backslash/Quote

What you would write:

string path = "C:\\Users\\folder";
string quote = "He said \"hello\"";

What happens: CParser crashes or produces garbled output. The \\ and \" escape sequences break the string parser.

Correct solution: Avoid backslash and quote characters in string literals entirely:

// Use forward slashes for paths
string path = "C:/Users/folder";

// Use single quotes or rephrase to avoid embedded double quotes
string quote = "He said 'hello'";

// Use string concatenation if you absolutely need special chars
// (still risky — test thoroughly)

Note: \n, \r, and \t escape sequences DO work. Only \\ and \" are broken.

---

9. No Variable Redeclaration in else-if Blocks

What you would write:

if (condA)
{
    string msg = "Case A";
    Print(msg);
}
else if (condB)
{
    string msg = "Case B";  // Same variable name in sibling block
    Print(msg);
}

What happens: Compile error: "multiple declaration of variable 'msg'". Enforce Script treats variables in sibling if/else if/else blocks as sharing the same scope.

Correct solution — unique names:

if (condA)
{
    string msgA = "Case A";
    Print(msgA);
}
else if (condB)
{
    string msgB = "Case B";
    Print(msgB);
}

Correct solution — declare before the if:

string msg;
if (condA)
{
    msg = "Case A";
}
else if (condB)
{
    msg = "Case B";
}
Print(msg);

---

10. No Ternary in Variable Declaration

Related to gotcha #1, but specific to declarations:

What you would write:

string label = isAdmin ? "Admin" : "Player";

Correct solution:

string label;
if (isAdmin)
    label = "Admin";
else
    label = "Player";

---

11. Object.IsAlive() Does NOT Exist on Base Object

What you would write:

Object obj = GetSomething();
if (obj.IsAlive())  // Check if alive

What happens: Compile error or runtime crash. IsAlive() is defined on EntityAI, not on Object.

Correct solution:

Object obj = GetSomething();
EntityAI eai;
if (Class.CastTo(eai, obj) && eai.IsAlive())
{
    // Safely alive
}

---

12. No nullptr — Use NULL or null

What you would write:

if (obj == nullptr)

What happens: Compile error. The nullptr keyword does not exist.

Correct solution:

if (obj == null)    // lowercase works
if (obj == NULL)    // uppercase also works
if (!obj)           // idiomatic null check (preferred)

---

13. switch/case Does NOT Fall Through

What you would write (expecting C/C++ fall-through):

switch (value)
{
    case 1:
    case 2:
    case 3:
        Print("1, 2, or 3");  // In C++, cases 1 and 2 fall through to here
        break;
}

What happens: Only case 3 executes the Print. Cases 1 and 2 are empty — they do nothing and do NOT fall through.

Correct solution:

if (value >= 1 && value <= 3)
{
    Print("1, 2, or 3");
}

// Or handle each case explicitly:
switch (value)
{
    case 1:
        Print("1, 2, or 3");
        break;
    case 2:
        Print("1, 2, or 3");
        break;
    case 3:
        Print("1, 2, or 3");
        break;
}

Note: break is technically optional in Enforce Script since there is no fall-through, but it is conventional to include it.

---

14. No Default Parameter Expressions

What you would write:

void Spawn(vector pos = GetDefaultPos())    // Expression as default
void Spawn(vector pos = Vector(0, 100, 0))  // Constructor as default

What happens: Compile error. Default parameter values must be literals or NULL.

Correct solution:

void Spawn(vector pos = "0 100 0")    // String literal for vector — OK
void Spawn(int count = 5)             // Integer literal — OK
void Spawn(float radius = 10.0)      // Float literal — OK
void Spawn(string name = "default")   // String literal — OK
void Spawn(Object obj = NULL)         // NULL — OK

// For complex defaults, use overloads:
void Spawn()
{
    Spawn(GetDefaultPos());  // Call the parametric version
}

void Spawn(vector pos)
{
    // Actual implementation
}

---

15. JsonFileLoader.JsonLoadFile Returns void

What you would write:

MyConfig cfg = JsonFileLoader<MyConfig>.JsonLoadFile(path);
// or:
if (JsonFileLoader<MyConfig>.JsonLoadFile(path, cfg))

What happens: Compile error. JsonLoadFile returns void, not the loaded object or a bool.

Correct solution:

MyConfig cfg = new MyConfig();  // Create instance first with defaults
JsonFileLoader<MyConfig>.JsonLoadFile(path, cfg);  // Populates cfg in-place
// cfg now contains loaded values (or still has defaults if file was invalid)

Note: The newer JsonFileLoader<T>.LoadFile() method returns bool, but JsonLoadFile (the commonly seen version) does not.

---

16. No #define Value Substitution

What you would write:

#define MAX_PLAYERS 60
#define VERSION_STRING "1.0.0"
int max = MAX_PLAYERS;

What happens: Compile error. Enforce Script #define only creates existence flags for #ifdef checks. It does not support value substitution.

Correct solution:

// Use const for values
const int MAX_PLAYERS = 60;
const string VERSION_STRING = "1.0.0";

// Use #define only for conditional compilation flags
#define MY_MOD_ENABLED

---

17. No Interfaces / Abstract Classes (Enforced)

What you would write:

interface ISerializable
{
    void Serialize();
    void Deserialize();
}

abstract class BaseProcessor
{
    abstract void Process();
}

What happens: The interface and abstract keywords do not exist.

Correct solution: Use regular classes with empty base methods:

// "Interface" — base class with empty methods
class ISerializable
{
    void Serialize() {}     // Override in subclass
    void Deserialize() {}   // Override in subclass
}

// "Abstract" class — same pattern
class BaseProcessor
{
    void Process()
    {
        ErrorEx("BaseProcessor.Process() must be overridden!", ErrorExSeverity.ERROR);
    }
}

class ConcreteProcessor extends BaseProcessor
{
    override void Process()
    {
        // Actual implementation
    }
}

The compiler does NOT enforce that subclasses override the base methods. Forgetting to override silently uses the empty base implementation.

---

18. No Generics Constraints

What you would write:

class Container<T> where T : EntityAI  // Constrain T to EntityAI

What happens: Compile error. The where clause does not exist. Template parameters accept any type.

Correct solution: Validate at runtime:

class EntityContainer<Class T>
{
    void Add(T item)
    {
        // Runtime type check instead of compile-time constraint
        EntityAI eai;
        if (!Class.CastTo(eai, item))
        {
            ErrorEx("EntityContainer only accepts EntityAI subclasses");
            return;
        }
        // proceed
    }
}

---

19. No Enum Validation

What you would write:

EDamageState state = (EDamageState)999;  // Expect error or exception

What happens: No error. Any int value can be assigned to an enum variable, even values outside the defined range.

Correct solution: Validate manually:

bool IsValidDamageState(int value)
{
    return (value >= EDamageState.PRISTINE && value <= EDamageState.RUINED);
}

int rawValue = LoadFromConfig();
if (IsValidDamageState(rawValue))
{
    EDamageState state = rawValue;
}
else
{
    Print("Invalid damage state: " + rawValue.ToString());
    EDamageState state = EDamageState.PRISTINE;  // fallback
}

---

20. No Variadic Parameters

What you would write:

void Log(string format, params object[] args)
void Printf(string fmt, ...)

What happens: Compile error. Variadic parameters do not exist.

Correct solution: Use string.Format with fixed parameter counts, or use Param classes:

// string.Format supports up to 9 positional arguments
string msg = string.Format("Player %1 at %2 with %3 HP", name, pos, hp);

// For variable-count data, pass an array
void LogMultiple(string tag, array<string> messages)
{
    foreach (string msg : messages)
    {
        Print("[" + tag + "] " + msg);
    }
}

---

21. No Nested Class Declarations

What you would write:

class Outer
{
    class Inner  // Nested class
    {
        int value;
    }
}

What happens: Compile error. Classes cannot be declared inside other classes.

Correct solution: Declare all classes at the top level, use naming conventions to show relationships:

class MySystem_Config
{
    int value;
}

class MySystem
{
    ref MySystem_Config m_Config;
}

---

22. Static Arrays Are Fixed-Size

What you would write:

int size = GetCount();
int arr[size];  // Dynamic size at runtime

What happens: Compile error. Static array sizes must be compile-time constants.

Correct solution:

// Use a const for static arrays
const int BUFFER_SIZE = 64;
int arr[BUFFER_SIZE];

// Or use dynamic arrays for runtime sizing
array<int> arr = new array<int>;
arr.Resize(GetCount());

---

23. array.Remove Is Unordered

What you would write (expecting order preservation):

array<string> items = {"A", "B", "C", "D"};
items.Remove(1);  // Expect: {"A", "C", "D"}

What happens: Remove(index) swaps the element with the last element, then removes the last. Result: {"A", "D", "C"}. Order is NOT preserved.

Correct solution:

// Use RemoveOrdered for order preservation (slower — shifts elements)
items.RemoveOrdered(1);  // {"A", "C", "D"} — correct order

// Use RemoveItem to find and remove by value (also ordered)
items.RemoveItem("B");   // {"A", "C", "D"}

---

24. No #include — Everything via config.cpp

What you would write:

#include "MyHelper.c"
#include "Utils/StringUtils.c"

What happens: No effect or compile error. There is no #include directive.

Correct solution: All script files are loaded through config.cpp in the mod's CfgMods entry. File loading order is determined by the script layer (3_Game, 4_World, 5_Mission) and alphabetical order within each layer.

// config.cpp
class CfgMods
{
    class MyMod
    {
        type = "mod";
        dependencies[] = { "Game", "World", "Mission" };

        class defs
        {
            class gameScriptModule
            {
                files[] = { "MyMod/Scripts/3_Game" };
            };
            class worldScriptModule
            {
                files[] = { "MyMod/Scripts/4_World" };
            };
            class missionScriptModule
            {
                files[] = { "MyMod/Scripts/5_Mission" };
            };
        };
    };
};

---

25. No Namespaces

What you would write:

namespace MyMod { class Config { } }
namespace MyMod.Utils { class StringHelper { } }

What happens: Compile error. The namespace keyword does not exist. All classes share a single global scope.

Correct solution: Use naming prefixes to avoid conflicts:

class MyConfig { }          // MyFramework
class MyAI_Config { }       // MyAI Mod
class MyM_MissionData { }   // MyMissions Mod
class VPP_AdminConfig { }     // VPP Admin

---

26. String Methods Modify In-Place

What you would write (expecting a return value):

string upper = myString.ToUpper();  // Expect: returns new string

What happens: ToUpper() and ToLower() modify the string in place and return void.

Correct solution:

// Make a copy first if you need the original preserved
string original = "Hello World";
string upper = original;
upper.ToUpper();  // upper is now "HELLO WORLD", original unchanged

// Same for TrimInPlace
string trimmed = "  hello  ";
trimmed.TrimInPlace();  // "hello"

---

27. ref Cycles Cause Memory Leaks

What you would write:

class Parent
{
    ref Child m_Child;
}
class Child
{
    ref Parent m_Parent;  // Circular ref — both ref each other
}

What happens: Neither object is ever garbage collected. The reference counts never reach zero because each holds a ref to the other.

Correct solution: One side must use a raw (non-ref) pointer:

class Parent
{
    ref Child m_Child;  // Parent OWNS the child (ref)
}
class Child
{
    Parent m_Parent;    // Child REFERENCES the parent (raw — no ref)
}

---

28. No Destructor Guarantee on Server Shutdown

What you would write (expecting cleanup):

void ~MyManager()
{
    SaveData();  // Expect this runs on shutdown
}

What happens: Server shutdown may kill the process before destructors run. Your save never happens.

Correct solution: Save proactively at regular intervals and on known lifecycle events:

class MyManager
{
    void OnMissionFinish()  // Called before shutdown
    {
        SaveData();  // Reliable save point
    }

    void OnUpdate(float dt)
    {
        m_SaveTimer += dt;
        if (m_SaveTimer > 300.0)  // Every 5 minutes
        {
            SaveData();
            m_SaveTimer = 0;
        }
    }
}

---

29. No Scope-Based Resource Management (RAII)

What you would write (in C++):

{
    FileHandle f = OpenFile("test.txt", FileMode.WRITE);
    // f automatically closed when scope ends
}

What happens: Enforce Script does not close file handles when variables go out of scope (even with autoptr).

Correct solution: Always close resources explicitly:

FileHandle fh = OpenFile("$profile:MyMod/data.txt", FileMode.WRITE);
if (fh != 0)
{
    FPrintln(fh, "data");
    CloseFile(fh);  // Must close manually!
}

---

30. GetGame().GetPlayer() Returns null on Server

What you would write:

PlayerBase player = PlayerBase.Cast(GetGame().GetPlayer());
player.DoSomething();  // CRASH on server!

What happens: GetGame().GetPlayer() returns the local player. On a dedicated server, there is no local player — it returns null.

Correct solution: On server, iterate the player list:

#ifdef SERVER
    array<Man> players = new array<Man>;
    GetGame().GetPlayers(players);
    foreach (Man man : players)
    {
        PlayerBase player;
        if (Class.CastTo(player, man))
        {
            player.DoSomething();
        }
    }
#else
    PlayerBase player = PlayerBase.Cast(GetGame().GetPlayer());
    if (player)
    {
        player.DoSomething();
    }
#endif

---

31. Klasy sealed nie mogą być rozszerzane (1.28+)

Od DayZ 1.28 kompilator Enforce Script wymusza słowo kluczowe sealed. Klasa lub metoda oznaczona sealed nie może być dziedziczona ani nadpisywana. Jeśli spróbujesz rozszerzyć zapieczętowaną klasę:

// Jeśli BI oznaczy SomeVanillaClass jako sealed:
class MyClass : SomeVanillaClass  // BŁĄD KOMPILACJI w 1.28+
{
}

Sprawdź zrzut vanillowych skryptów pod kątem klas oznaczonych sealed, zanim spróbujesz po nich dziedziczyć. Jeśli musisz zmodyfikować zachowanie zapieczętowanej klasy, użyj kompozycji (opakuj ją) zamiast dziedziczenia.

---

32. Limit parametrów metody: maksymalnie 16 (1.28+)

Enforce Script zawsze miał limit 16 parametrów na metodę, ale przed wersją 1.28 było to ciche przepełnienie bufora powodujące losowe crasha. Od wersji 1.28 kompilator produkuje twardy błąd:

// BŁĄD KOMPILACJI w 1.28+ — przekracza 16 parametrów
void MyMethod(int a, int b, int c, int d, int e, int f, int g, int h,
              int i, int j, int k, int l, int m, int n, int o, int p,
              int q)  // 17. parametr = błąd
{
}

Rozwiązanie: Zrefaktoruj przekazywanie klasy lub tablicy zamiast poszczególnych parametrów.

---

33. Ostrzeżenia atrybutu Obsolete (1.28+)

DayZ 1.28 wprowadził atrybut Obsolete. Funkcje i klasy oznaczone [Obsolete] generują ostrzeżenia kompilatora. Te API nadal działają, ale są zaplanowane do usunięcia w przyszłej aktualizacji. Sprawdź wyjście kompilacji pod kątem ostrzeżeń o przestarzałości i migruj na zalecany zamiennik.

---

34. Błąd porównania int.MIN

Porównania obejmujące int.MIN (-2147483648) dają nieprawidłowe wyniki:

int val = 1;
if (val < int.MIN)  // Ewaluuje się jako TRUE — powinno być false
{
    // Ten blok wykonuje się nieprawidłowo
}

Unikaj bezpośrednich porównań z int.MIN. Zamiast tego użyj zapisanej stałej lub porównuj z konkretną wartością ujemną.

---

35. Negacja boolowska elementu tablicy nie działa

Bezpośrednia negacja boolowska elementów tablicy się nie kompiluje:

array<int> list = {0, 1, 2};
if (!list[1])          // NIE KOMPILUJE SIĘ
if (list[1] == 0)      // Działa — użyj jawnego porównania

Przy testowaniu prawdziwości elementów tablicy zawsze używaj jawnych sprawdzeń równości.

---

36. Złożone wyrażenie w przypisaniu do tablicy powoduje crash

Przypisanie złożonego wyrażenia bezpośrednio do elementu tablicy może spowodować segmentation fault:

// CRASHUJE w runtime
m_Values[index] = vector.DistanceSq(posA, posB) <= distSq;

// BEZPIECZNE — użyj zmiennej pośredniej
bool result = vector.DistanceSq(posA, posB) <= distSq;
m_Values[index] = result;

Wyniki złożonych wyrażeń zawsze zapisuj w zmiennej lokalnej przed przypisaniem do tablicy.

---

37. foreach na wartości zwracanej z metody powoduje crash

Użycie foreach bezpośrednio na wartości zwracanej z metody powoduje wyjątek null pointer przy drugiej iteracji:

// CRASHUJE na 2. elemencie
foreach (string item : GetMyArray())
{
}

// BEZPIECZNE — najpierw zapisz w zmiennej lokalnej
array<string> items = GetMyArray();
foreach (string item : items)
{
}

---

38. Priorytet operatorów bitowych vs porównania

Operatory bitowe mają niższy priorytet niż operatory porównania, zgodnie z regułami C/C++:

int flags = 5;
int mask = 4;
if (flags & mask == mask)      // ŹLE: ewaluowane jako flags & (mask == mask)
if ((flags & mask) == mask)    // DOBRZE: zawsze używaj nawiasów

---

39. Puste bloki #ifdef / #ifndef powodują crash

Puste bloki preprocesora warunkowego — nawet te zawierające wyłącznie komentarze — powodują segmentation fault:

#ifdef SOME_DEFINE
    // Ten blok zawierający tylko komentarz powoduje SEGFAULT
#endif

Zawsze dołącz co najmniej jedną instrukcję wykonywalną lub całkowicie pomiń blok.

---

40. GetGame().IsClient() zwraca False podczas ładowania

Podczas fazy ładowania klienta GetGame().IsClient() zwraca false, a GetGame().IsServer() zwraca true — nawet na klientach. Zamiast tego użyj IsDedicatedServer():

// NIEWIARYGODNE podczas fazy ładowania
if (GetGame().IsClient()) { }   // false podczas ładowania!
if (GetGame().IsServer()) { }   // true podczas ładowania, nawet na kliencie!

// WIARYGODNE
if (!GetGame().IsDedicatedServer()) { /* kod klienta */ }
if (GetGame().IsDedicatedServer())  { /* kod serwera */ }

Wyjątek: Jeśli musisz obsługiwać tryb offline/singleplayer, IsDedicatedServer() zwraca false również dla listen serverów.

---

41. Komunikaty błędów kompilacji wskazują zły plik

Gdy kompilator napotka niezdefiniowaną klasę lub konflikt nazw zmiennych, zgłasza błąd na końcu ostatniego pomyślnie sparsowanego pliku — nie w faktycznym miejscu błędu. Jeśli widzisz błąd wskazujący na plik, którego nie modyfikowałeś, prawdziwy błąd jest w pliku parsowanym zaraz po nim.

---

42. Pliki crash_*.log to nie crashe

Pliki logów o nazwie crash_<data>_<czas>.log zawierają wyjątki runtime, nie faktyczne segmentation fault. Nazwa jest myląca — to błędy skryptów, nie crashe silnika.

---

Coming From C++

If you are a C++ developer, here are the biggest adjustments:

C++ Feature	Enforce Script Equivalent
std::vector	array<T>
std::map	map<K,V>
std::unique_ptr	ref / autoptr
dynamic_cast<T*>	Class.CastTo() or T.Cast()
try/catch	Guard clauses
operator+	Named methods (Add())
namespace	Name prefixes (My, VPP_)
#include	config.cpp files[]
RAII	Manual cleanup in lifecycle methods
Multiple inheritance	Single inheritance + composition
nullptr	null / NULL
Templates with constraints	Templates without constraints + runtime checks
do...while	while (true) { ... if (!cond) break; }

---

Coming From C#

C# Feature	Enforce Script Equivalent
interface	Base class with empty methods
abstract	Base class + ErrorEx in base methods
delegate / event	ScriptInvoker
Lambda =>	Named methods
?. null conditional	Manual null checks
?? null coalescing	if (!x) x = default;
try/catch	Guard clauses
using (IDisposable)	Manual cleanup
Properties { get; set; }	Public fields or explicit getter/setter methods
LINQ	Manual loops
nameof()	Hardcoded strings
async/await	CallLater / timers

---

Coming From Java

Java Feature	Enforce Script Equivalent
interface	Base class with empty methods
try/catch/finally	Guard clauses
Garbage collection	ref + reference counting (no GC for cycles)
@Override	override keyword
instanceof	obj.IsInherited(typename)
package	Name prefixes
import	config.cpp files[]
enum with methods	enum (int-only) + helper class
final	const (for variables only)
Annotations	Not available

---

Coming From Python

Python Feature	Enforce Script Equivalent
Dynamic typing	Static typing (all variables typed)
try/except	Guard clauses
lambda	Named methods
List comprehension	Manual loops
**kwargs / *args	Fixed parameters
Duck typing	IsInherited() / Class.CastTo()
__init__	Constructor (same name as class)
__del__	Destructor (~ClassName())
import	config.cpp files[]
Multiple inheritance	Single inheritance + composition
None	null / NULL
Indentation-based blocks	{ } braces
f-strings	string.Format("text %1 %2", a, b)

---

Tabela szybkiej referencji

Feature	Exists?	Workaround
Ternary ? :	No	if/else
do...while	No	while + break
try/catch	No	Guard clauses
Multiple inheritance	No	Composition
Operator overloading	Index only	Named methods
Lambdas	No	Named methods
Delegates	No	ScriptInvoker
\\ / \" in strings	Broken	Avoid them
Variable redeclaration	Broken in else-if	Unique names or declare before if
Object.IsAlive()	Not on base Object	Cast to EntityAI first
nullptr	No	null / NULL
switch fall-through	No	Each case is independent
Default param expressions	No	Literals or NULL only
#define values	No	const
Interfaces	No	Empty base class
Generic constraints	No	Runtime type checks
Enum validation	No	Manual range check
Variadic params	No	string.Format or arrays
Nested classes	No	Top-level with prefixed names
Variable-size static arrays	No	array<T>
#include	No	config.cpp files[]
Namespaces	No	Name prefixes
RAII	No	Manual cleanup
GetGame().GetPlayer() server	Returns null	Iterate GetPlayers()

---

Nawigacja

Previous	Up	Next
1.11 Error Handling	Part 1: Enforce Script	Part 2: Mod Structure