On Thu, Sep 13, 2001 at 12:51:43PM -0300, Anthony Yuen wrote:
>
> Hi, I found another "problem" that "bugs" me (pun intended!).
> In the class collaboration diagram that is generated, I think something
> is not quite right. Let me give an example:
>
> class A { /* some methods */ };
>
> class B { std::vector<A *> vec; };
>
> I'm just using the std::vector as an example. It can be any
> kind of (STL) container. Even though this strongly suggests that
> class B somehow uses class A for "something" (in my case, B *does*
> make use of A, which is why B stores a vector of pointers to A),
> Doxygen does not conclude that there is collaboration between A and B.
> This can be extended to include the use of smart pointers stored
> in a container.
>
> I'm interested to know if this is the intended behaviour. If
> so, what is the reason behind? If not, maybe this is a bug?
Currently this is intended behaviour, but I would like to hear what other
people think about this. Should template arguments, such as in the example
above, be visualised in collaboration diagrams? and if so, how? Does UML
cover these kind of relations?
Regards,
Dimitri
|
