by
Anonymous Coward
on 2012年03月14日 22時18分
(#2117693)
> The layout of each object depends on its class. Some classes appear to have binary compatible function tables but there is no indication that they have any common parent classes (like in other OO languages). Furthermore, the location of the function table is not fixed: some classes have it at offset 0 of the instance, but some does not.
オブジェクト内での関数テーブルの位置が不定らしいのと
> Member functions can be referenced by the object’s function table (like “virtual” functions in C++) or they can be called directly. In most object-oriented languages, member functions receive the “this” parameter that references the instance of the object, and there is a calling convention that defines the location of the parameter – either in a register, or in stack. This is not the case for the Duqu Framework classes – they can receive “this” parameter in any register or in stack.
下手 (スコア:0)
プログラミングが下手なだけだったりして
Re: (スコア:0)
C(not C++)を使ってオブジェクト指向したら、挙げられてる特徴を満たすコードになりそうですねぇ。
Re: (スコア:0)
それ何てX11
Re:下手 (スコア:0)
> The layout of each object depends on its class. Some classes appear to have binary compatible function tables but there is no indication that they have any common parent classes (like in other OO languages). Furthermore, the location of the function table is not fixed: some classes have it at offset 0 of the instance, but some does not.
オブジェクト内での関数テーブルの位置が不定らしいのと
> Member functions can be referenced by the object’s function table (like “virtual” functions in C++) or they can be called directly. In most object-oriented languages, member functions receive the “this” parameter that references the instance of the object, and there is a calling convention that defines the location of the parameter – either in a register, or in stack. This is not the case for the Duqu Framework classes – they can receive “this” parameter in any register or in stack.
thisパラメータが特定のレジスタやスタック位置で渡されるわけではないらしいところが珍しいですね
C+ライブラリ(あるいはcfront的なプリプロセッサ)の可能性もあると思います