Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using another class as a parameter or result #23

Open
simonjwright opened this issue Sep 8, 2023 · 0 comments
Open

Using another class as a parameter or result #23

simonjwright opened this issue Sep 8, 2023 · 0 comments

Comments

@simonjwright
Copy link
Owner

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!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@simonjwright