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

Methods not memorized, ruins inheritance #314

Open
The-Markitecht opened this issue Oct 6, 2024 · 2 comments
Open

Methods not memorized, ruins inheritance #314

The-Markitecht opened this issue Oct 6, 2024 · 2 comments

Comments

@The-Markitecht
Copy link
Contributor

Welcome to Jim version 0.84
. info patchlevel
0.82-134-gdcea42c
. class a {}
a
. a method m {} {}
a m
. a methods
. class b a {}
b
. b method z {} {}
b z
. b methods
. 

Per the docs, class a should have listed out 1 method. b should have listed out 2 methods. Instead neither got their methods memorized at all. Therefore b could not inherit the methods from a. Therefore inheritance is totally non-functional.

I first noticed this when 'super' couldn't find the method. But the issue looks much broader than that.

I'll see if I can dig down to the root cause this week.

@The-Markitecht
Copy link
Contributor Author

Root cause is #315 .

The-Markitecht added a commit to TheMarkitecht/jimtcl that referenced this issue Oct 6, 2024
Methods not memorized, ruins inheritance
@The-Markitecht
Copy link
Contributor Author

fixed in PR #316

msteveb pushed a commit that referenced this issue Oct 7, 2024
Methods not memorized, ruins inheritance
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

1 participant