invalid non-declared variable

[rocorona]

can you reproduce/explain this behavior?

In a master script:

DEFINE TRANSLUCENT_FILL "test1" zero,2,3,4,5,6,7,8, 0.25
zero=0
DEFINE TRANSLUCENT_FILL "test2" zero,2,3,4,5,6,7,8, 0.25

when checking these instructions, ArchiCAD reports "insufficient parameters" for the first DEFINE, where a non-declared variable is used.
Thes second one is copy-pasted, to avoid any possible difference, but the zero is declared, and it works.

--Roberto Corona--

[David Maudlin]

Roberto:

My guess is that the first (undeclared) "zero" is read as a string expression (text) where ArchiCAD expects a numeric expression (number). Defining "zero" as a number corrects this error.

David

[rocorona]

this could be true, but we know that undeclared variables are initialized as numbers.
And, in fact, if I test it (at the script first line) with VARTYPE (zero) it says is "1" (number) not "2" (string).

Just discovered that an explicit use of "zero" as number (before the first DEFINE command) seems to "force" a declaration.
For examples, using a simple

x=zero+zero

the error message disappears.

[Anonymous]

rocorona wrote:
this could be true, but we know that undeclared variables are initialized as numbers.
And, in fact, if I test it (at the script first line) with VARTYPE (zero) it says is "1" (number) not "2" (string).

Just discovered that an explicit use of "zero" as number (before the first DEFINE command) seems to "force" a declaration.
For examples, using a simple

x=zero+zero

the error message disappears.

Roberto,

I would have answered the same as David, pat1 to pat8 are integers. Is there something else to understand?
But your second post makes more sense.

Yes, I get the same result/alerts.
May be zero is a reserved keyword for GS programmers. Anyway, thanks for the info.

[David Maudlin]

There are a number of ways to initialize the variable.
1. Add a new parameter to the part with the Variable "zero".
2. At the beginning of the Master Script add "zero=zero".
3. At the beginning of the Master Script add "Print zero".

I am sure there are more, for what it is worth.

David

[ztaskai]

When using numeric variables, you should initialize them before their value is used for the first time. The good way to do this is the following for a variable which is OK to start from a given constant:

isOkToStartFomZero = 0
shouldStartFrom3 = 3

AC13 will have a GDL warning to warn developers about uninitialized variables. It helps you stay in picture about what is happening.

Regards,
Zsolt

[Anonymous]

I checked, zero is not a reserved keyword.
x = zero+zero is the same as writing zero = 0
zero can be replaced by any variable.

ztaskai wrote:
When using numeric variables, you should initialize them before their value is used for the first time. The good way to do this is the following for a variable which is OK to start from a given constant:

isOkToStartFomZero = 0
shouldStartFrom3 = 3

AC13 will have a GDL warning to warn developers about uninitialized variables. It helps you stay in picture about what is happening.

Regards,
Zsolt

Good point.

[Anonymous]

Hi Zsolt,

ztaskai wrote:
AC13 will have a GDL warning to warn developers about uninitialized variables. It helps you stay in picture about what is happening.

Just to tease us a little... In a scale of -10 to 10 which do you think will be our impression about AC13 GDL new features?...
Thank you for the news!

[Karl Ottenstein]

ztaskai wrote:
AC13 will have a GDL warning to warn developers about uninitialized variables.

That's great news, Zsolt.

The old behavior of an uninitialized variable being treated as a zero-value has 'bitten' too many newcomers to GDL, and even old timers. A simple typo results in a variable with a zero value which can take considerable time to track down and debug. The warning will be a great help to everyone.

Certainly, some old (user written) library parts will need to have initialization statements added, but that is for the good IMHO. It was lazy programming to intentionally assume an uninitialized variable would be zero.

Thanks,
Karl

[Laszlo Nagy]

ztaskai wrote:
AC13 will have a GDL warning to warn developers about uninitialized variables.

What would also be good is to extend this behavior to all error cases in GDL, not just uninitialized variable. I could even imagine ArchiCAD giving an advice in the error message on how to fix it.
For example, when the "Fill not found at line xxx" message, the message could also say that this and this parameter or line of code calls for a fill with this fill index, but it does not exist, check in your Fill Types Dialog or the Attribute Manager or whatever blablabla.
The point would be to enable people to solve the problem themselves.