Biography has not been added
- Problems with inheritance by composition
I am reading these series of articles rather late - however coudn't the linux kernel container_of macro simplify code in getting the outer structure ? Also I wouldn't prefer that client code do any traversal - ideally client code sees only opaque types and public API functions. The API function implementation can hide the 'dirt' and invoke the polymorphic function via the vtable - this minimizes redundant typing of the structure pointer everywhere in client code.