RealInterval Setting Notes

by default enableRealInterval is set to false, no pharo methods will be overwritten and RealInterval will not work correctly. if you set it to true these methods will be overwritten:

• Number>>raisedTo:
• Number>>raisedToInteger:
• Float>>/ or SmallFloat64>>/ and BoxedFloat64>>/
• Integer>>//
• SmallInteger>>quo:
• Fraction>>raisedToInteger:

if you set it to false again, these methods will be reset to their original form. this overwriting and resetting happens via RBTransformationRules, hence if these methods are changed by eg you or a newer version, those changes will be incorporated in the overwriting, which makes this approach much more robust than my stupid simple original approach. but any changes to these methods by you should be done after enableRealInterval is set to false first. during normal use of pharo it is my experience that having set enableRealInterval to true has no bad consequences. the tests set enableRealInterval to true in their setUp and restore the original setting afterwards in the tearDown, hence they work irrespective of the setting. this simple use of a setting also allowed me to simplify the ConfigurationOfRealInterval and eliminate the dirty trick i had used there, hence i made a completely new configuration.

Back to Basic Use