Cheryl Scodario wrote:Hey Jason! Thanks as always. I am just wondering what does a byte-code looks like? Because I feel like so far I have been using text file that contains strings. But I did use InputStreamReader once, but I don't remember why?
Campbell Ritchie wrote:You might do well to look at a book like this one. The same publishers have one about C#, but there is a more recent edition than that described in our reviews pages.
Hansjoachim Vonhortenschiem wrote:So, in my minds eye, I can envision an object consisting of members that are part of that objects blueprint (class), members that are inherited from the parents blueprint(thereby becoming part of the childs blueprint), and those members of the parents blueprint that, though part of the child object, are not part of the childs blueprint. These last members still occupy a space in memory and are accessible via parent provided accessor methods.
The upside is that you can have a unique instance of a parents private instance variable to compliment a child object (assuming you have a way to access it).
The downside is if the same unique instance of a parents instance varaible is hugh(!) in memory and you have no use for it whatever.
It just seems hard to believe that Java-Authors would allow such a system in which memory could be wasted in such a way......