Pharo Issue Tracker - Manuscript (Case [Issue]21340) Kernel - isReadOnlyObject should not fail when VM do not support write barrier

Manuscript Notification

	Denis Kudryashov opened Case 21340: isReadOnlyObject should not fail when VM do not support write barrier and assigned it to Everyone: Bug in Kernel: 1. Pharo Image • You are subscribed to this case

Now ARM VM do not support write barrier. And with latest Pharo 7 it is impossible to modify classes because o #isReadOnlyObject check.

So this method should never fail.

	Priority: 5 – Fix If Time		Status: Work Needed
	Assigned to: Everyone		Milestone: Pharo7.0

Go to Case

No longer need updates? Unsubscribe from this case.

Don't want Manuscript notifications anymore? Update your preferences.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker