topic Incomprehensible grammar problem in Libraries & objects

Incomprehensible grammar problem

Anonymous — Wed, 17 Jul 2019 06:57:08 GMT

HI!
I have been programming for a long time, and I can't understand some basic errors in GDL. E.g:


x  =  0.38
x2 = 1.08
if x=x2 then print 1 else print 2

check script : use of real types can result...
???
I can't use the equal sign, so every time I use very cumbersome code to judge
I really can't stand this problem.

I can only write this way.


x  =  0.38
x2 = 1.08
if x-x2 then 
  print 2
else
  print 1
endif

Re: Incomprehensible grammar problem

Lingwisyer — Wed, 17 Jul 2019 08:50:40 GMT

I have no issue using the equal sign. I do believe I have an issue doing a If - Then - Else on a single line. I can do an If - Then on a single line, but if I add an Else I need to split the actions into separate lines. I will check tomorrow if I remember...

Ling.

Re: Incomprehensible grammar problem

Barry Kelly — Wed, 17 Jul 2019 09:10:40 GMT

There is no problem with the if/then/else all on one line.
It is simply a warning to say it is not a good idea to equate numbers with each other.
Your original script may work, but it is not a good idea to use it unless you can be sure of the accuracy of the numbers.

I don't understand it all myself, but I believe there is a level of accuracy that GDL uses.
Have a look at this....

You can write an equation that does not use = and you can specify the level of accuracy that you want to compare.

Barry,

Re: Incomprehensible grammar problem

Anonymous — Thu, 18 Jul 2019 02:01:16 GMT

"=" The equal sign can only support integers
So I can only use the greater than or less than the number to judge, can not use the equal sign, so very inaccurate

I don't report errors when I write like this.


     if  x<= 0.1 and x>0.09 then print 1

Re: Incomprehensible grammar problem

Lingwisyer — Thu, 18 Jul 2019 02:15:41 GMT

Oh. That error. For user inputs, I have instead been writing

If a <> b then d else c

Ling.

Re: Incomprehensible grammar problem

Ralph Wessel — Thu, 18 Jul 2019 08:45:33 GMT

The key issue here is precision. It's generally not helpful to issue architectural documentation with precision smaller than 1mm, and construction tolerances are generally not that tight. You want to be aware of that when scripting for objects because it's very easy to be far more precise than is helpful to the user.

For example, if an object is supposed to display a specific label or illustration if the length is 5m, what should happen if the length is 5.00001m, i.e.a difference of 0.01mm? The user won't be able to detect that difference visually or using dimensions because ARCHICAD won't display dimensions to that precision. So the user might have something which looks exactly like 5m, but the object acts as though it isn't.

This is why ARCHICAD is warning you when you say things like:

if length = 5 then

. Specify a level of precision in your script and then use it for all floating point comparisons, e.g.:

eps = 1e-4
if abs(length - 5) < eps then

GS is right in calling this to your attention – handling precision incorrectly can be really irritating (or costly) for the end user otherwise.