AppletTalk.com

Brian · Guest

Hi -

What does a typical Java stcak frame look like? I'm not familiar
with the machine architecture but I'd imagine some minimum number
of registers get pushed per method call. And I'd imagine it's
non-trivial seeing as the stack frame can be overflowed easily.
Is there any intelligence to strip stack frames to a minimum?

So the idea is that OO languages offer encapsulation whereby
methods hide data completely. But each of those methods come
at a performance hit. Or is it trivial?

Let's say there are two IO stream classes, buffered or otherwise.
The calling method simply wants to get data from one stream to
the other as quickly as possible.

Isn't having a "isAvailable()" (or similar) call right in the
middle of that loop counterproductive?

Curiosity is killing me. I never quite find this stuff in
books or classes. I would guess default access modifier
(package?) has some strategic value for allowing nearby classes
to access data directly.

Any ideas or comments appreciated.