Is it correct to always set the attribute type in vex wrangle code ?

[nikaragua86 9]

Hello, friends! I`ve got some issues when started coding in vex with the default float type attribute creation, so i got a habit to always set the attribute type, even in calculations, to prevent the possibility of attribute type errors.

Like this for example:

v@direction = v@initial_position - v@P;

It works fine, and i am really comfortable with it,  but I wonder is it correct in the meaning of

1) Good programming style. 

2) VEX language work under the hood - maybe VEX is re-declaring the attributes again, when they are used in this way.

Thank you!

[Jesper Rahlff 62]

there is no downside to doing that as far as I am aware, except you have to type a few more characters.

However it is looked at as extremely good practice to do so, so I would continue doing it if I were you

[nikaragua86 9]

Thank you very much!

[fencer 152]

Prefer not to add type for global variables like @P, @N, @v.... but if there is a custom variable like f@mysuperval, yes it must be.

[nikaragua86 9]

Thank you!

[pusat 123]

I only add type if the attribute is unknown to Houdini and it's not a float. Using @ for unknown attributes will declare it as a float.

[nikaragua86 9]

Aha, thank you.

[acey195 148]

In my opinion explicitly typing your attributes is good practice;
in particular, for not accidentally using floats when you can/should use integers(if you want to check against specific numbers)

if(x==6) is way better than if(x==6.0) for example,

[nikaragua86 9]

Thank you!