PT Forum

XanthorXIII Joined: 13th May 2011
Location:

Posted: 9th Sep 2011 20:18

Ether I'm going crazy or something is really funny here with Globals and dividing.

This code below does not use Globals, this produces the expected result of 6.25 and 4.166667

+ Code Snippet

SetDisplayAspect(320.0/480.0)
dw# = 100.0/16.0
dh# = 100.0/24.0

do
    PRINT(dw#)
    PRINT(dh#)
    Sync()
loop

The Code below uses globals and does not get the same results.

+ Code Snippet

SetDisplayAspect(320.0/480.0)
GLOBAL dw# = 100.0/16.0
GLOBAL dh# = 100.0/24.0

do
    PRINT(dw#)
    PRINT(dh#)
    Sync()
loop

Please confirm what values you get. This is a huge error that needs to get fixed ASAP.

Jimmy Joined: 20th Aug 2003
Location: Back in the USA

Posted: 9th Sep 2011 20:26

I think this is because you're initializing your globals with a math operation instead of a constant value, which is a bug, yeah, but it can easily be worked around:

+ Code Snippet

SetDisplayAspect(320.0/480.0)
Global dw# = 100.0
Global dh# = 100.0

dw# = dw#/16.0
dh# = dh#/24.0

do
    PRINT(dw#)
    PRINT(dh#)
    Sync()
loop

XanthorXIII Joined: 13th May 2011
Location:

Posted: 9th Sep 2011 21:57

I'm just about ready to throw in the towel on Tier 1 and just move over to Tier 2. The problem with Tier 1 is while it looks good on paper, there's a lot of fixes that need to be done.

Jimmy Joined: 20th Aug 2003
Location: Back in the USA

Posted: 9th Sep 2011 22:53

I agree. While I'm not going to throw in the towel, I am going to give it time to improve before I try to code anything major in it.

Conjured Entertainment Joined: 12th Sep 2005
Location: Nirvana

Posted: 10th Sep 2011 3:31

Have you tried declaring it as Global on one line, then assign the value on a separate line?

+ Code Snippet

SetDisplayAspect(320.0/480.0)

GLOBAL dw#
dw# = 100.0/16.0

GLOBAL dh#
dh# = 100.0/24.0

do
    PRINT(dw#)
    PRINT(dh#)
    Sync()
loop

DMXtra Joined: 28th Aug 2002
Location: United States

Posted: 10th Sep 2011 5:44

Why not post the bug here so it can be fixed:

http://code.google.com/p/agk/issues/list

XanthorXIII Joined: 13th May 2011
Location:

Posted: 10th Sep 2011 5:50

I can do that but that's not how it's suppose to work.
I'll do it anyway just so I can continue working.
And yes, I have posted it to the Bug List on the Google Code Community for the AGK.

Conjured Entertainment Joined: 12th Sep 2005
Location: Nirvana

Posted: 10th Sep 2011 17:45

I can do that but that's not how it's suppose to work.

I know, but what does work and what is supposed to work are two separate things.

I ran into problems with globals too, but when I declared it as global on a separate line from the value assignment, my problems went away.
It's not that big of a deal to declare it on a searate line anyway, so that is the initialization style I am using now.

Good Luck

LeeBamber Joined: 21st Jan 2000
Location: England

Posted: 11th Sep 2011 0:35

The benefit to the literal values in the declaration line is that those values are pre-loaded into the data variable before the code begins, meaning you get started a few instructions quicker. If we all agree we don't need that performance boost, I can permanently modify the compiler to always treat the initialiser in real-time rather than at compile time. If anyone has an input on this subject, use this thread and I'll check back on it before making any changes to the compiler. If there are any issues you might be experiencing with T1, please use the issues board to let us know about then. We feel T1 has great potential, and we want to make sure this potential is realised as soon as possible.

<1 >

Sign In