Skip to content

Conversation

@masinter
Copy link
Member

fixes #859

This change was put in by me as a hack. \PUTBASEFIXP already checks against bignums. It is only because it was under an UNINTERRUPTABLY that it called RAID rather than signalling a Lisp error.

The code here could be improved but putting it back seems like the prudent approach-- something else is going wrong well before we get here.

@masinter masinter requested a review from rmkaplan July 26, 2022 17:42
@rmkaplan
Copy link
Contributor

rmkaplan commented Jul 26, 2022 via email

@nbriggs
Copy link
Contributor

nbriggs commented Jul 26, 2022

We should probably not merge debugging hacks into master. If it's debugging code that others should try, it's easy enough to push a branch to github so they can get it... no PR is necessary, just announce the branch name.

Since \PUTBASEFIXP does the check for the right type and calls \LISPERROR if it's bad I'm OK with removing the extra check.

Copy link
Contributor

@rmkaplan rmkaplan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rmkaplan rmkaplan merged commit 16517cd into master Aug 11, 2022
@masinter masinter deleted the bignum-test-was-wrong-fix branch August 12, 2022 21:57
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.

The BIGNUM declaration is not in EXPORTS.ALL

4 participants