Clément Bera wrote:
MyClass>>#foo <compilerOptions: #(- optInlineIf)> ^ #myNonBooleanObject ifTrue: [ 1 ] ifFalse: [ 0 ]
There are different options like this one. I wrote them down here to remember (section compilerOptions): http://clementbera.wordpress.com/2013/05/28/modular-compilation-with-opal/ But it is not very nicely written, I've just write it to remember ..
The nice thing on Smalltalk is that it is readable. I would recommond to use full names for the new compiler options: + optInlineIf => optionInlineIf + optInlineIfNil => optionInlineIfNil ... With just "opt" no one knows if it really means "option" or "optimization"/"optimized" or "object pointer", ... https://pharo.fogbugz.com/default.asp?11036 Bye T.
Am 27.06.2013 um 09:49 schrieb "Torsten Bergmann" <astares@gmx.de>:
Clément Bera wrote:
MyClass>>#foo <compilerOptions: #(- optInlineIf)> ^ #myNonBooleanObject ifTrue: [ 1 ] ifFalse: [ 0 ]
There are different options like this one. I wrote them down here to remember (section compilerOptions): http://clementbera.wordpress.com/2013/05/28/modular-compilation-with-opal/ But it is not very nicely written, I've just write it to remember ..
The nice thing on Smalltalk is that it is readable. I would recommond to use full names for the new compiler options:
+ optInlineIf => optionInlineIf + optInlineIfNil => optionInlineIfNil ...
With just "opt" no one knows if it really means "option" or "optimization"/"optimized" or "object pointer", ...
+1 Norbert
https://pharo.fogbugz.com/default.asp?11036
Bye T.
participants (2)
-
Norbert Hartl -
Torsten Bergmann