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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Pharo Issue Tracker
Manuscript Notification
avatar
Enhancement in Project:  Compiler Opal: 1. Pharo Image  •  You are subscribed to this case
Ah I saw the comments on the pull request but not the ones here (Sorry I never know if I need to look at the pull request comments or in the bug tracker since different people post on both).

Yes there was a problem yesterday, I fixed it, but the fix used 'obj class isImmediateClass' and that was called at the beginning of the bootstrap script, and at this point, '1 class isImmediateClass' answers false instead of true for some reason. So I changed the code for '{Character.SmallInteger.SmallFlaot64} includes: obj class', we will see if this new expression works at the beginning of the bootstrap and if so this pull request can be merged.
Priority Priority: 3 – Must Fix Status Status: Resolved (Fix Review Needed)
Assigned To Assigned to: Marcus Denker Milestone Milestone: Pharo7.0

Go to Case
No longer need updates? Unsubscribe from this case.

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

Manuscript

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