Andre Poenitz wrote:
Maybe I still did not fully understand the concepts.
Are 'DocumentClass' and 'LayoutFile' two completely distinct concepts
such that we never can exchange a 'DocumentClass' for a 'LayoutFile'
(but that happen to share a common implementation via some 'TextClass'
base right now) _or_ do we have the case that we basically have a
concept 'TextClass' coming in two varieties?
The latter. They're both subclasses of TextClass.
The question is not how it is currently implemented but what the concept
looks like. Do we have functions that accept an 'opaque' TextClass, or
do we always have _either_ a DocumentClass _or_ a LayoutFile?
Sorry, no, we always have one or the other, I think. There may be one
exception somewhere, but I've worked to make them as separate as possible.
By the way, I keep forgetting (but will add a comment) that we CANNOT
and MUST NOT have the LayoutList in these classes be a container of
pointers. The comment explains why, in r23703.
rh
