>>>IOW, even though I don't like my code to depend on scenarios, they do exist and dictate the behavior.
>>
>>You don't like scenarios for you code pieces? You mean you don't like to have a framework?
>
>I don't like my code to react to a list of possible events, because there's always some more that weren't on the list, always something you didn't think of. I prefer my code to do a certain set of actions, and be as much as possible resistant to a "scenario we didn't think of". So instead of coding for cases, I prefer to code the general behavior and then have the scenarios just perform a set of distinct (and best if independent) steps in this behavior.
>
>Hard to put into words, but this is my way of trying to think the code into a more robust whole.

This's why I don't use my own right alignment numeric input class at UT's download section... :)