Skip to content

fixes inconsistencies with the tagof operator #245

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

Merged
merged 1 commit into from
Apr 22, 2018

Conversation

YashasSamaga
Copy link
Member

#160

The standalone tagof operator tries to export tall tags which it works with.

The tagof operator when used as a default argument checks if the tag is zero before exporting.

As the zero tag identifier cannot be exported (even if its PUBLICTAG bit is set), it makes sense to use 0 as tag identifier instead of 0 | PUBLICTAG.

This commit changes the standalone tagof operator behavior so that the zero tag identifier does not get its PUBLICTAG bit set.

The standalone tagof operator tries to export tall tags which it works with.

The tagof operator when used as a default argument checks if the tag is zero before exporting.

As the zero tag identifier cannot be exported (even if its `PUBLICTAG` bit is set), it makes sense to use `0` as tag identifier instead of `0 | PUBLICTAG`.

This commit changes the standalone tagof operator behaviour so that the zero tag identifier does not get its `PUBLICTAG` bit set.
@Zeex Zeex merged commit a840b4a into pawn-lang:master Apr 22, 2018
@YashasSamaga YashasSamaga deleted the fix-i160 branch October 11, 2020 11:38
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

Successfully merging this pull request may close these issues.

2 participants