-
Notifications
You must be signed in to change notification settings - Fork 46
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
Metaclass (and TraitedMetaclass) DNU #classVariableNamed:ifAbsent:
#2327
Comments
How do you get this? |
That one bubbled up from the system somewhere. I don’t remember exactly the steps. There was another way in the inspector. Let me try to record steps |
I got some more info from the debug log in case it helps:
|
Pending resolution of feenkcom/gtoolkit/issues/2327 OT: NB. this alternate implementation from Date was removed from UFFA: ```smalltalk subtractYears: anInteger (self monthIndex = 2 and: [ self dayOfMonth = 29 ]) ifTrue: [ self error: 'Subtracting years from a leap year is undefined' ]. ^ Date year: self year - anInteger month: self monthName day: self dayOfMonth. ``` Noting that here because it differs from our implementation and can't remember why!
I cannot reproduce this. Can you reproduce it consistently in the latest version? |
Not consistently, but sporadically in 0.8.1145. I've experienced this in the scenario I mention above (Class inspector as opposed to snippet in playground) consistently, but not ALL the time, so sporadic since ~0.8.1100 |
Hi This turned out to be a bug in Pharo. Metaclass is not polymorphic with Class... I reported it and it is fixed in Pharo 10. pharo-project/pharo#10334 I think we should add a patch to Pharo while building GT :) |
A patch for P9 would be good. It seems trivial: https://github.com/seandenigris/Pharo-Enhancements/blob/7a59a2f790990595a9632844a60e0e8a44909729/src/PharoEnhancements-GToolkit/Metaclass.extension.st Thanks for following up. |
…ss to be polymorphic with Class
added a patch |
I thought I had reported this, but don't see an issue...
The text was updated successfully, but these errors were encountered: