Report From here on out, I'm using OO.... in Object-Oriented Programming Posted January 30, 2012 At least you already learned it, in a more classical sense. It's usually quite a task to "get" OO when you've only been working with (relatively) strict dataflow most of your life. I remember the simultaneous look of wonderment, confusion and disgust on my students' faces when I used to teach the Endevo GOOP course. I wasn't aware that inheritance per se was "anti-dataflow". I do understand that byref implementations could be seen that way in certain use cases, or as an overall model for organizing OO within a dataflow environment/language, by I really don't get how byval implementations inherently are anti-dataflow. Am I missing something?