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.

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

Minor: Missing pretty-print of mk_aliastag? #34

Open
CThuleHansen opened this issue May 3, 2024 · 3 comments
Open

Minor: Missing pretty-print of mk_aliastag? #34

CThuleHansen opened this issue May 3, 2024 · 3 comments
Assignees

Comments

@CThuleHansen
Copy link
Contributor

Hi Nick,

It seems some of the VDM is not formatted nicely?
image

@nickbattle
Copy link
Collaborator

Ah yes, that was a bit lazy, I admit. In FMI2, variable aliasing uses a combination of the variable reference and a "Kind" (integer, real etc). To print that out, I just "toString" the AliasTag type, rather than formatting it nicely.

So the formatting could be better, but it looks like you have a case where there is no "Kind"? Can you give me the modelDescription.xml for this so I can debug it?

@nickbattle nickbattle self-assigned this May 3, 2024
@CThuleHansen
Copy link
Contributor Author

CThuleHansen commented May 3, 2024

I just asked the engineer to give it to me, will be back :)

@nickbattle
Copy link
Collaborator

A quick thought. The toString should have shown mk_AliasTag(723, <Real>). But often angle brackets are sensitive in various editors (like this one!), so I just had to put the above in backticks. Is it possible the blank Kind in your example is a screen-grab of such an editor and that the <Real> is actually being printed on stdout?

That still leaves the formatting issue, but I can't think why else the Kind is not appearing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants