- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #940: 21952-FileSystemStoresignalFileDoesNotExist-creates-bad-exception

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #940 was: SUCCESS. The Pull Request #1407 was integrated: "21952-FileSystemStoresignalFileDoesNotExist-creates-bad-exception" Pull request url: https://github.com/pharo-project/pharo/pull/1407 Issue Url: https://pharo.fogbugz.com/f/cases/21952 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 23, 2018

[Pharo 7.0-dev] Build #939: 16076-make-environment-work-for-Opal

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #939 was: FAILURE. The Pull Request #1406 was integrated: "16076-make-environment-work-for-Opal" Pull request url: https://github.com/pharo-project/pharo/pull/1406 Issue Url: https://pharo.fogbugz.com/f/cases/16076 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Sean P. DeNigris

Marcus Denker-4 wrote > indeed.. I still believe that we should late-bind global access :-) I'll keep +1-ing every time you mention this ha ha ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 13:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 23 May 2018, at 13:30, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >>> Marcus Denker-4 wrote >>>> method := Smalltalk compiler >>>> environment: environment; >>>> compile: 'tt ^MyClassâ. >>> >>> Awesome! Is it possible to override a global from /within/ a method (e.g. in >>> a test)? >> >> I think at the class level by manipulating that class compiler > > Yes. You can override the class side method: > > in Behaviour, it is defined as > > compiler > "Answer a compiler appropriate for source methods of this class." > > ^self compilerClass new > environment: self environment; > class: self > > so you can just > > compiler > âChange the compiler environment " > > ^super compiler > environment: self myEnvironment > > > and it should work. Here we can see, too, that we need to do more work. In Behaviour: environment "Return the environment in which the receiver is visible" ^Smalltalk globals For classes to automatically compile with the environment they are in, we somehow need to return here that environmentâ¦ Marcus

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 13:30, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> Marcus Denker-4 wrote >>> method := Smalltalk compiler >>> environment: environment; >>> compile: 'tt ^MyClassâ. >> >> Awesome! Is it possible to override a global from /within/ a method (e.g. in >> a test)? > > I think at the class level by manipulating that class compiler Yes. You can override the class side method: in Behaviour, it is defined as compiler "Answer a compiler appropriate for source methods of this class." ^self compilerClass new environment: self environment; class: self so you can just compiler âChange the compiler environment " ^super compiler environment: self myEnvironment and it should work. an a per method bases, we can only manipulate the compiler via Pragmas to set options: <compilerOptions: #(+ optionInlineTimesRepeat)> for example. > (and > forcing a method recompile...) > indeed.. I still believe that we should late-bind global access :-) Marcus

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Thierry Goubier

2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Marcus Denker-4 wrote >> method := Smalltalk compiler >> environment: environment; >> compile: 'tt ^MyClassâ. > > Awesome! Is it possible to override a global from /within/ a method (e.g. in > a test)? I think at the class level by manipulating that class compiler (and forcing a method recompile...) Thierry > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Sean P. DeNigris

Marcus Denker-4 wrote > method := Smalltalk compiler > environment: environment; > compile: 'tt ^MyClassâ. Awesome! Is it possible to override a global from /within/ a method (e.g. in a test)? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 11:49, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Marcus, > > can you do inheritence / masking of a hierarchy of system dictionaries ? > > Could be used to make "kind of" sandboxes, around, say, user code so > that it does not have the ability to override a certain system core. > Yes, I was starting to think about exactly thatâ¦ I will do some experiments. Marcus

May 23, 2018

[Pharo 7.0-dev] Build #938: 21953-Fixing-failing-test-in-Traits-TraitFileOutTest

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #938 was: SUCCESS. The Pull Request #1405 was integrated: "21953-Fixing-failing-test-in-Traits-TraitFileOutTest" Pull request url: https://github.com/pharo-project/pharo/pull/1405 Issue Url: https://pharo.fogbugz.com/f/cases/21953 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Thierry Goubier

Marcus, can you do inheritence / masking of a hierarchy of system dictionaries ? Could be used to make "kind of" sandboxes, around, say, user code so that it does not have the ability to override a certain system core. Thierry 2018-05-23 11:45 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >> A second iteration now makes it work correctly for assignments: >> >> https://github.com/pharo-project/pharo/pull/1397 >> >> Smalltalk compiler >> bindings: {(#test -> Point)} asDictionary; >> evaluate: 'test := 42â. > > While #bindings: allows us now to add additional bindings or override global bindings from Smalltalk globals, there is another feature missing that would be nice: be able to set the global environment > > I want to be able to tell the compiler: Do not use Smalltalk globals, but this SystemDictionary instead. > > https://github.com/pharo-project/pharo/pull/1406 > > with this, we can create a SystemDictionary with just one binding in it: > > environment := SystemDictionary new. > environment at: #MyClass put: Point. > > then we compile a method: > > method := Smalltalk compiler > environment: environment; > compile: 'tt ^MyClassâ. > > and if we execute it, it shows that compilation used the environment: > > return := method valueWithReceiver: nil arguments: #(). > self assert: return equals: Point. > > If we try to compile a ref to Object, we get a nil ref: > > method := Smalltalk compiler > environment: environment; > compile: 'tt ^Object'. > return := method valueWithReceiver: nil arguments: #(). > self assert: return equals: nil. > > But, as the Undeclared mechanism is not aware of it, it puts an undeclared for Object there. > > In the same direction, all objects the compiler creates come still from Smalltalk globals (CompiledMethod, all Literalsâ¦). > > But all this can be improved, we do pass the environment down the compiler chain already so that it is even available in the Parser/Scanner. Thus we could e.g. create Literals as instances from the classes in the environment. But how exactly has to be seen. > > Marcus > > >

May 23, 2018