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

abolish/2 needed #1476

Open
UWN opened this issue May 14, 2022 · 2 comments
Open

abolish/2 needed #1476

UWN opened this issue May 14, 2022 · 2 comments

Comments

@UWN
Copy link

UWN commented May 14, 2022

That is, abolish(PS,[force(true)])

Note that the ISO abolish/1 works only for dynamic code. Static predicates are not permitted. But when doing extensive testing (and it seems there are still issues in the WAM code generation), there is only one way: generate and test and abolish. Certainly, this makes only sense, after the memory management issues of assert/1 are solved.

@infradig
Copy link

Note: abolish(Name, Arity) is already a common thing.

@UWN
Copy link
Author

UWN commented May 16, 2022

Note: abolish(Name, Arity) is already a common thing.

This precludes further extensions. Think of predicate indicators vs non-terminal indicators.

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