Skip to content

Using another class as a parameter or result #23

Description

@simonjwright

This arose with SF bug 79, no longer visible, but traces visible in the SF_Bug_79 domain in Regressions.uml.

The fix there is very clumsy.

A better fix would generate with {Domain}.{Class}; in the using class’s package spec, and {Class}.Handle in its subprograms.

The second part is easy, but the first part would need a lot more work; and, interactions with other classes should be managed via relationships!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions