A little warning.. Gemini is not perfect til now. it will produce functional code but does not Know common Problems with the GDL-Interpreter-Tester in Archicad..And does not learn from one User to another. If You work with it - let it explicit Know of this:
(Gemini wrote this in englisch for You)
Subject: GDL Tip: Solving persistent "Real types" warnings and Array Index errors
Hi everyone,
While scripting complex objects (specifically involving the Accessories Add-on and dynamic coordinate arrays), I encountered some stubborn errors regarding array indexing that I wanted to share a solution for.
The Problem:
Even when loop variables are logically integers, the GDL interpreter (especially in the PARAMETER SCRIPT) often throws warnings or errors such as:
This happens even if the variable was defined previously, e.g.:
codeGdl
i = 1
val = myArray[i] ! <-- Can still throw errors or warnings
The Cause:
The GDL parser is extremely strict, particularly regarding calculations performed near or inside array brackets. It often treats the result of a calculation or a loop variable as a Floating Point (Real) number by default. Since array indices must be strict Integers, this causes conflicts.
The Solution: Aggressive Casting with INT()
It is often not enough to convert the variable just once at the beginning. You must use the INT() command directly inside the square brackets of the array query. This forces the parser to accept the value as an Integer at that exact moment.
Code Comparison:
❌ Risky (prone to warnings):
codeGdl
FOR i = 1 TO n
! Even if i is a loop variable, calculation results might be treated as Real
idx = (i-1)*2 + 1
! This often causes the "precision problems" warning:
val = coordArray[idx]
NEXT i
✅ Robust (Best Practice):
codeGdl
FOR i = 1 TO n
! 1. Cast the loop variable locally
i_int = INT(i)
! 2. Cast the calculation result
idx = INT( (i_int-1)*2 + 1 )
! 3. CRITICAL: Use INT() directly inside the brackets!
! This eliminates the warning completely.
val = coordArray[ INT(idx) ]
NEXT i
Since adopting this strict syntax ("Aggressive INT-Casting"), all precision warnings and unexplained index errors in my scripts have disappeared, and parameter stability (e.g., when geometry changes dynamically) is guaranteed.
I hope this helps anyone else who might be struggling with these specific GDL parser quirks!
end of Geminis warning.
There are several other solutions for this problem possible..
AC5.5-AC27EduAut, PC-Win10, MacbookAirM1, MacbookM1Max, Win-I7+Nvidia
