< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事(スレッド移動)
N :次の記事
|<:前のスレッド
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事(前)
<:同じ返事先を持つ記事(後)
---:分割してスレッド表示、再表示
| :分割して(縦)スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
I was wondering if someone could help me understand why there's a parallel =
class hierarchy - there's the 'real' class objects which holds onto instanc=
e methods, and the 'virtual' class object that holds onto class methods.
I can see how this design can make method lookup somewhat faster since it a=
voids having to do a test and branch operation before method dispatch.
But is there some other non-obvious corner case that drove this design? In =
other words, if there were an implementation that had a dictionary for inst=
ance methods and class methods on the same class object, would this break s=
omething?
Thanks,
-John