visser:
Because I want pretty much an event system out of this. Pretty much, accessing sensor values or motor directions when needed. Then destroyed, once accessed.
In a microprocessor, data like that is simply stored in an array. Not a complex "preference system."
visser:
I thought it was made clear, but it was not. I am trying to use the preference/attribute system to trigger tasks. So basically it is an event system in some way is it not? Hmmmm?
No, you have not been clear. As Nick points out you haven't said what you were trying to do and it makes it appear you are changing the requirements of your question. A "preference/attribute system" makes very little since on a microcontroller, so everyone here is struggling to understand what you are trying to accomplish.
Creating "events" to respond to "senor values" can easily (and most commonly) be done with if-statements or switch-cases.
visser:
AND BY THE WAY. Everyone has been telling me about the constraints to this, memory, yes I understand all of it, but I do not want to store them over a long period of time. So please get you replies on the topic and try to help me out.
What is "long period of time"? You keep using abstracts and not giving actual information. You aren't programming a PC. You claim to understand this, but I don't think you actually do.
It sounds like you are trying to store sensor values and act on them. You are significantly overcomplicating the situation with your high-level "preferences" system.