FogBugz (Case [Issue]11007) Compiler Opal - Pharo 3 now uses mustBeBooleanInMagic: by default

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

FogBugz (Case [Issue]11007) Compiler Opal - Pharo 3 now uses mustBeBooleanInMagic: by default

Pharo Issue Tracker
A FogBugz case was opened by Clement Bera.

Case ID:      11007
Title:        Pharo 3 now uses mustBeBooleanInMagic: by default
Status:       Work Needed
Category:     Bug
Project:      Compiler Opal
Area:         Misc
Priority:     2 - Really Important
Milestone:    Later
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/default.asp?11007

Here you can see :

Object>>mustBeBooleanIn: context
...
Smalltalk compilerClass = OpalCompiler
ifTrue: [ ^ self mustBeBooleanInMagic: context ].
...

The problem is this method is not finished, and even if finished, there should be a warning for newcomers.

At some point there was a setting, allowNonBooleanReceiver. Is it still somewhere ?

Because now by default I got :

IRPushClosureCopy(Object)>>doesNotUnderstand: #nextBytecodeOffsetAfterJump
AJComparison(Object)>>mustBeBooleanInMagic:
AJComparison(Object)>>mustBeBooleanIn:
AJComparison(Object)>>mustBeBoolean
...

Which is very confusing.


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=11007) from this case.

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