|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> Warp wrote:
> > Don't you mean that it moves the data one slot *up*
> Wet ink smears. Hence, people write from the top of the page towards the
> bottom. Hence, lower numbers in a list are higher on the page than higher
> numbers on a list.
It really becomes irritatingly confusing when people use the terms
"upcasting" and "downcasting" assuming that all the readers agree on what
they mean.
Heck, even *I* can't figure out which is which. In UML derived classes
are typically drawn *below* the base class, so "upcasting" would mean
casting from derived class to base class (I have seen this usage). On the
other hand, an inheritance hierarchy can be seen as a tree where the base
class is at the root (hence the name "base"). In this case "upcasting" would
be casting from the base class to the derived class (I have seen this usage
as well).
When I see someone using the terms, I just can't assume anything (unless
it can be unambiguously deduced from the context).
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |