Pharo Issue Tracker - Manuscript (Caso [Issue]21372) Compiler Opal - Introducing read-only literals settings and rewamp of Compiler settings

Manuscript Notification

	Pablo Tesone edited Case 21372: Introducing read-only literals settings and rewamp of Compiler settings: Enhancement in Compiler Opal: 1. Pharo Image • You are subscribed to this case

It seems that there are failing tests. I see that the tests failing look like the ones failing in development. However, it is also failing to print the stack trace, because the stack trace includes a character with a codepoint that is invalid. Maybe the VM crash is related to this recursive error.

	Priority: 3 – Must Fix		Status: Resolved (Fix Review Needed)
	Assigned to: Marcus Denker		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