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

Investigate Correct Usage of __SIGNED_INT and __UNSIGNED_INT #56

Open
montymxb opened this issue Feb 26, 2025 · 0 comments
Open

Investigate Correct Usage of __SIGNED_INT and __UNSIGNED_INT #56

montymxb opened this issue Feb 26, 2025 · 0 comments
Labels
priority-medium Should be resolved in 1-3 sprints

Comments

@montymxb
Copy link
Contributor

montymxb commented Feb 26, 2025

Docs state that __SIGNED_INT and __UNSIGNED_INT are injected under package declarations, as stated on page 190 of the 6.1 lang ref. However, even in the absence of a top-level package declaration, one is apparently synthesized for you:

If the source contains no PACKAGE statement, the
compiler effectively inserts one after the first set of *PROCESS statements...

As such, we've currently added these type aliases as built-ins, since they're available in almost all cases. However it needs to be investigated whether we can construct statements that would reference these types and exist outside a declared (or synthesized package). Lastly it's possible that, despite the documentation, we may be able to reference these injected aliases in such cases. If so we should promote this up to compiler-documentation discrepancy for 6.1

@montymxb montymxb added the priority-medium Should be resolved in 1-3 sprints label Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-medium Should be resolved in 1-3 sprints
Projects
None yet
Development

No branches or pull requests

1 participant