@Alzie said:
@Lithium said:
Not that I would ever code something like that, that would make a person into a wizbit I still want to give a shout out in thanks for this. I checked all the code I ported in and am not vulnerable to it, but at least I will try and break my u() habit, which I usually type just because it's more universal. I'd use v() except I hate having functions and databases on the same objects as actual code. Guess I'm weird like that... so get() here I come. I suppose those two extra characters won't kill me 🙂
To be clear, get and u do completely different things. Sometimes u is necessary, sometimes get is necessary. If you're using U to get an attribute and nothing more then you should be using get/xget. If you actually need to run code stored in an attribute you still want U. As for v, it's a shortcut for get that grabs an attribute relative to the object that it's ran on.
I had forgotten about needing U to run functions on another object, as you need to evaluate them and not 'get' them when I wrote that bit. A good reminder though 🙂 Thank you.
