Constants ... bug ...

[francoisg]

Hi,
I know the language as it currently stands does not support constant values, so I did the following: Create a Code Module called "Constants"
---------------------------------------------
'Code module
'Subs in this code module will be accessible from all modules.
Sub Process_Globals
abc = "a"
def = "12#"
End Sub
---------------------------------------------

When I now use code completion it give me the following options:
Constants._abc
Constants._def
If I however use it like that the compiler complains - if I use Constants.abc it works ...

 

[Erel]

Does it happen in the same module or from a different module?
You should "dim" the variables in order for them to appear.

 

[agraham]

You should "dim" the variables in order for them to appear.

I tried copying that Sub and have once seen the effect described for those non-Dimmed variables but I can't now repeat it. Normally they don't show up at all.

 

[francoisg]

Happens in a different module. It works perfectly without using dim, the only thing is code completion does not work as expected!

 

[agraham]

Looks like there is some odd bug in Intellisense. You (Erel) see Process_Globals where I don't (different thread) and OP here sees, apparently reproducibly, something I have only managed to replicate once but you (Erel) don't see at all (I assume).

 

[agraham]

I can now reliably reproduce this. It only occurs after compiling the program. Looks like the lack of Dim means that Intellisense is picking up the compiled Java name of the variable and not the B4A name.

 

[Erel]

Edit: It will be fixed. Undimmed variables should not appear at all.

 

[francoisg]

Sorry, no ...
I'll see if I can quickly slap something together and upload it for you ...

 

[Erel]

I've edited my previous post right after reading agraham's post. So there is no need to upload anything.