To be nil or not to be nil

[Resike]

I have an issue about an user reported possible bug:

Can this line cause an error like that?

if aura.Timer.enabled then
    --
end

Attempt to index field 'Timer' (a nil value).

Even when the Timer is really nil than why does it pop an error?

I can't reproduce the problem anyhow so i'm not sure what/why is this happening.

[Rilgamon]

A "key" can not be nil.

[Haleth]

The compiler is looking for the key 'enabled' in the table aura.Timer - only aura.Timer isn't a table, it's nil. That gives an error.

[zork]

if aura.Timer and aura.Timer.enabled then
...
end

[Resike]

Originally Posted by Haleth The compiler is looking for the key 'enabled' in the table aura.Timer - only aura.Timer isn't a table, it's nil. That gives an error.

But when the Timer is nil then the Timer.enabled is not gonna be nil?

[Haleth]

You can't treat a nil value (Timer, in this case) as a table.

You have to make sure that it isn't nil before you start to do table lookups (Timer.enabled).

[Resike]

Originally Posted by Haleth You can't treat a nil value (Timer, in this case) as a table. You have to make sure that it isn't nil before you start to do table lookups (Timer.enabled).

I see, my bad then.