Re: DOCBOOK: ClassSynopsis revisited again

[Stefan Seefeld <seefelds@MAGELLAN.UMontreal.CA>]

What about representing the relationship as an entity in it's
own right ?

<classsynopsis language="cpp">
  <classname>Rectangle_with_data</classname>
  <inherits kind="virtual"><classname>Shape</classname></inherits>
  <inherits kind="virtual"><classname>Data_container</classname></inherits>
</classsynopsis>

I find this more logic than your way of expressing it since in fact the
three classes all play different roles in this diagram. Only the first
is subject to definition while the other two are assumed to be known
already. The treatment in XML and it's stylesheets should reflect that.

may be 'inherits' needs to be replaced by different types or it should
get further attributes to distinguish (if the language needs it) between
inherit, implement, extend etc.

Regards,	Stefan
_______________________________________________________              

Stefan Seefeld
Departement de Physique
Universite de Montreal
email: seefelds@magellan.umontreal.ca

_______________________________________________________

      ...ich hab' noch einen Koffer in Berlin...