- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Problem with asClass usage

by Ben Coman

I believe #asClass itself was introduced for a use case to simplify Workspace "user interactive" Gofer scripts to retrieve and load Configurations. Since this is through away code its not covered by your modularity concerns, and I'm not sure if it came before or after its friends, but can we retain or substitute something to avoid needing ugly "(Smalltalk at: #ConfigurationOfXXX) load" ? This is a "first impression" consideration for people dealing with Configurations for the first time (even thought we now have Configuration Browser). The use case is that newbies will copy-paste a script from a web site to Playground and execute the whole script resulting in a error "Unknown class ConfigurationOfXXX." They don't know to execute in two separate steps, first "Gofer ... load" then "ConfigurationOfXXX load". Alternatively, what if the Metacello package extended Gofer with a method #configurationOf: so websites can show... config := Gofer new url: 'http://smalltalkhub.com/mc/MyProject/main' package: 'MyXXXPackage'; load; configurationOf: 'XXX' "return class ConfigurationOfXXX" config load. ...so the compiler is dealing with a variable "config" rather than class 'ConfigurationOfXXX' that it doesn't know yet, or a further altenative... Gofer new url: 'http://smalltalkhub.com/mc/MyProject/main' package: 'MyXXXPackage'; load; configurationOf: 'XXX' do: [ :config | config load ]; configurationOf: 'YYY' do: [ :config | config load ]. cheers -ben On 10/04/2015 4:32 am, "stepharo" <stepharo(a)free.fr> wrote: > Hi > > We want to raise a strong warning against the extension of the use of > asClass and friends. > asClass should not be used in Pharo distribution. I will propose to > deprecate it. > > We are working on dependency analysis, module system, remote debugging and > asClass introduces > lose class references and many related problems. > > I would like to remove this behavior because it is clear that it will just > grow up and lead to deadcode and ugly dependencies. > > First, most of the time you can avoid to query Smalltalk globals at: and > that BY CONSTRUCTION a software system should be built and it should > define its own customization. > > > Second, at least use self class environment at: #foo > > Why is it much much much better? because it does not rely on String class > resolution and as such > is much more modular. You do not want to have the resolution of a symbol > related to the place where String is defined but on where your code is > actually. > > Imagine that tomorrow your code is in its own module. Then you want to > know from your code point of you > if a binding exist not from the one of environment in which String is. > > > > > here are some examples: > > ============================== > quadrangleClass > ^ 'QuadrangleForTesting' asClass > > Strange it simply breaks. Of course it broke the smallLint rule. > > ============================== > Metacello should better define OSProcess as a dependent.Because it is not > clear what will happen > if if not there? > > extractRepositoryFrom: zipFile to: directory > "unzip <zipFile> into <directory>" > > | out err proc errorMessage | > out := FileStream forceNewFileNamed: '/tmp/zip.out'. > err := FileStream forceNewFileNamed: '/tmp/zip.err'. > errorMessage := ''. > [ > proc := #OSProcess asClass thisOSProcess > forkJob: '/usr/bin/unzip' > arguments: > {'-u'. > zipFile. > '-d'. > directory} > environment: nil > descriptors: (Array with: nil with: out with: err). > > ================== > > I do not get why we need this funky logic. > > openInBrickWindowLabeled: aLabel > > #GLMSystemWindowBrick asClassIfAbsent: [ > ^ self asMorph openInWindow ]. > > ^ #GLMSystemWindowBrick asClass new > label: aLabel; > color: Color transparent; > addBrickBack: ( > GLMBrick new > vSpaceFill > > > window > "Answer the receiver's window." > #GLMWindowBrick asClassIfAbsent: [ > ^ self ownerThatIsA: SystemWindow ]. > > ^ (self ownerThatIsA: #GLMWindowBrick asClass) > ifNil: [ self ownerThatIsA: SystemWindow ] > > > > sendUsageData: aBoolean > | settingsClass | > settingsClass := #GTSpotterEventRecorderSettings asClassIfAbsent: [ ^ > self ]. > ^ settingsClass sendUsageData: aBoolean > > > sendUsageData > | settingsClass | > settingsClass := #GTSpotterEventRecorderSettings asClassIfAbsent: [ ^ > false ]. > ^ settingsClass sendUsageData > > >

April 10, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by ClÃ©ment Bera

I was using it frequently too and I have never experienced any issues... 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess(a)web.de>: > > 2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> No Debug Tests? >> >> Geez, I am using that all the time. >> > > And you're never encountered this issue 14689 > <https://pharo.fogbugz.com/default.asp?14689>? > Or did this work in older versions? > > > > >> >> Phil >> >> >> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >>> wrote: >>> > >>> > Nicolai Hess wrote >>> >> >>> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >>> > >>> > Ah, I miss that too! From that thread, it seems it was removed >>> temporarily >>> > until we have real breakpoints. Is there an issue for its return? >>> > >>> >>> Not yet. >>> >>> Marcus >>> >> >> >

April 10, 2015

Re: [Pharo-dev] New Cog VMs available

by Tobias Pape

Sorry the noise, did not look on whereto I replied. :/ Best -Tobias On 10.04.2015, at 00:16, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Updated on the CI :) > > Best > -Tobias > On 09.04.2015, at 23:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3308/. >> >> CogVM binaries as per VMMaker.oscog-eem.1178/r3308 >> >> Plugins: >> Integrate Nicolas' fixes that use positiveMachineIntegerFor: for pointers. >> >> Newspeak: >> Print a warning in the method shared under multiple selectors scenario. >> >> Implement outer sends as clean sends just like implicit receiver sends. Add >> ObjectRepresentation>>illegalClassTag and use it for initializing and unlinking >> implicit and outer sends. >> >> Newspeak & Sista: >> The multiple bytecode set block initial nil counters need >> to be specific to the bytecode set in effect. >> >> Spur: >> Implement Clement's much better solution for the stale supersend problem. >> Place code at the send site for super sends to follow stale forwarded >> receivers. This parallels the interpreter implementation. >> >> Beef up the post-become scan of send sites to >> unlink all send sites that link to an invalid class tag. >> >> Cogit: >> Optimize StackToRegisterMappingCogit>>genReturnReceiver >> to not load ReceiverResultReg if it already contains self. >> >> Revise method map generation to provide multiple send type annotations. Add >> an IsAnnotationExtension annotation type that implicitly has a zero displacement >> and uses its displacement bits to extend the preceeding IsSendCall annotation. >> This allows us to eliminate all the exotic entry-points and keep only the >> checked and unchecked entries. >> >> Change IA32's genPushRegisterArgsForNumArgs: to not smash TempReg now that it >> is used in directed super send trampolines. >> >> Use PushCq to pass small integer constants in the trampolines instead of >> smashing TempReg, which is now used to hold the directed supersend argument. >> Add support for PushCq. Could use PushCw but on x86 PushCq is a lot shorter. >> >> Mac builds: Use UTC as the timezone for the build timestamp. Using the local >> timezone doesn't work :(.

April 9, 2015

Re: [Pharo-dev] New Cog VMs available

by Tobias Pape

Updated on the CI :) Best -Tobias On 09.04.2015, at 23:28, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > ... at http://www.mirandabanda.org/files/Cog/VM/VM.r3308/. > > CogVM binaries as per VMMaker.oscog-eem.1178/r3308 > > Plugins: > Integrate Nicolas' fixes that use positiveMachineIntegerFor: for pointers. > > Newspeak: > Print a warning in the method shared under multiple selectors scenario. > > Implement outer sends as clean sends just like implicit receiver sends. Add > ObjectRepresentation>>illegalClassTag and use it for initializing and unlinking > implicit and outer sends. > > Newspeak & Sista: > The multiple bytecode set block initial nil counters need > to be specific to the bytecode set in effect. > > Spur: > Implement Clement's much better solution for the stale supersend problem. > Place code at the send site for super sends to follow stale forwarded > receivers. This parallels the interpreter implementation. > > Beef up the post-become scan of send sites to > unlink all send sites that link to an invalid class tag. > > Cogit: > Optimize StackToRegisterMappingCogit>>genReturnReceiver > to not load ReceiverResultReg if it already contains self. > > Revise method map generation to provide multiple send type annotations. Add > an IsAnnotationExtension annotation type that implicitly has a zero displacement > and uses its displacement bits to extend the preceeding IsSendCall annotation. > This allows us to eliminate all the exotic entry-points and keep only the > checked and unchecked entries. > > Change IA32's genPushRegisterArgsForNumArgs: to not smash TempReg now that it > is used in directed super send trampolines. > > Use PushCq to pass small integer constants in the trampolines instead of > smashing TempReg, which is now used to hold the directed supersend argument. > Add support for PushCq. Could use PushCw but on x86 PushCq is a lot shorter. > > Mac builds: Use UTC as the timezone for the build timestamp. Using the local > timezone doesn't work :(.

April 9, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Nicolai Hess

2015-04-09 23:38 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > No Debug Tests? > > Geez, I am using that all the time. > And you're never encountered this issue 14689 <https://pharo.fogbugz.com/default.asp?14689>? Or did this work in older versions? > > Phil > > > On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> >> wrote: >> > >> > Nicolai Hess wrote >> >> >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… >> > >> > Ah, I miss that too! From that thread, it seems it was removed >> temporarily >> > until we have real breakpoints. Is there an issue for its return? >> > >> >> Not yet. >> >> Marcus >> > >

April 9, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Thierry Goubier

Le 09/04/2015 23:34, Yuriy Tymchuk a Ã©crit : > Sad. It happens to me quite a lot. So is this an issue in monticello? I don't know. Something is happening somewhere with the source code, and as a consequence Monticello test for finding the changes mark everything as changed. I'm pushing a solution for that symptom. https://pharo.fogbugz.com/default.asp?15321 But I haven't found the reason. Something is switching the line endings on some of the MC definitions, and I don't know who or what is doing that (and not everytime). Thierry > > > >> On 08 Apr 2015, at 22:13, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> Uko, >> >> you seem to have the same bug Johan is describing. >> >> MC seems to loose the contents of a package working copy, and hence is unable to build a correct diff. >> >> I've seen it happen at times, but rarely enough so I didn't pay attention to it. >> >> Thierry >> >> Le 08/04/2015 09:44, Yuriy Tymchuk a Ã©crit : >>> >>>> On 07 Apr 2015, at 12:16, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>>> >>>> Le 07/04/2015 11:01, Yuriy Tymchuk a Ã©crit : >>>>> Hi, thank you very much for investigating this. >>>> >>>> You're working on it too :) >>>> >>>>> These are the steps to reproduce: >>>>> >>>>> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git) >>>>> 2. Add it as gitfiletree repo to the pharo image. >>>>> 3. Change something, commit part of the changes with Komitter. >>>>> 4. Change something more. >>>>> 5. Open Komitter, you should see a strange diff. >>>>> 6. Select 1 or 2 methods & commit them. >>>>> 7. Now you should have only 2 methods in your repo. >>>> >>>> I did, and I don't see anything suspicious. Browsing the repository at each step gave me the complete package as expected (minus the unsaved changes, of course). >>>> >>>> Can you show a screenshot at step 5? >>> >>> Iâve done a screen recording https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov >>> >>> Uko >>> >>>> >>>> Thierry >>>> >>> >>> >>> >> >> > > > >

April 9, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by phil＠highoctane.be

No Debug Tests? Geez, I am using that all the time. Phil On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > > > Nicolai Hess wrote > >> > http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… > > > > Ah, I miss that too! From that thread, it seems it was removed > temporarily > > until we have real breakpoints. Is there an issue for its return? > > > > Not yet. > > Marcus >

April 9, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Yuriy Tymchuk

Sad. It happens to me quite a lot. So is this an issue in monticello? > On 08 Apr 2015, at 22:13, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Uko, > > you seem to have the same bug Johan is describing. > > MC seems to loose the contents of a package working copy, and hence is unable to build a correct diff. > > I've seen it happen at times, but rarely enough so I didn't pay attention to it. > > Thierry > > Le 08/04/2015 09:44, Yuriy Tymchuk a Ã©crit : >> >>> On 07 Apr 2015, at 12:16, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> Le 07/04/2015 11:01, Yuriy Tymchuk a Ã©crit : >>>> Hi, thank you very much for investigating this. >>> >>> You're working on it too :) >>> >>>> These are the steps to reproduce: >>>> >>>> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git) >>>> 2. Add it as gitfiletree repo to the pharo image. >>>> 3. Change something, commit part of the changes with Komitter. >>>> 4. Change something more. >>>> 5. Open Komitter, you should see a strange diff. >>>> 6. Select 1 or 2 methods & commit them. >>>> 7. Now you should have only 2 methods in your repo. >>> >>> I did, and I don't see anything suspicious. Browsing the repository at each step gave me the complete package as expected (minus the unsaved changes, of course). >>> >>> Can you show a screenshot at step 5? >> >> Iâve done a screen recording https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov >> >> Uko >> >>> >>> Thierry >>> >> >> >> > >

April 9, 2015

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3308/. CogVM binaries as per VMMaker.oscog-eem.1178/r3308 Plugins: Integrate Nicolas' fixes that use positiveMachineIntegerFor: for pointers. Newspeak: Print a warning in the method shared under multiple selectors scenario. Implement outer sends as clean sends just like implicit receiver sends. Add ObjectRepresentation>>illegalClassTag and use it for initializing and unlinking implicit and outer sends. Newspeak & Sista: The multiple bytecode set block initial nil counters need to be specific to the bytecode set in effect. Spur: Implement Clement's much better solution for the stale supersend problem. Place code at the send site for super sends to follow stale forwarded receivers. This parallels the interpreter implementation. Beef up the post-become scan of send sites to unlink all send sites that link to an invalid class tag. Cogit: Optimize StackToRegisterMappingCogit>>genReturnReceiver to not load ReceiverResultReg if it already contains self. Revise method map generation to provide multiple send type annotations. Add an IsAnnotationExtension annotation type that implicitly has a zero displacement and uses its displacement bits to extend the preceeding IsSendCall annotation. This allows us to eliminate all the exotic entry-points and keep only the checked and unchecked entries. Change IA32's genPushRegisterArgsForNumArgs: to not smash TempReg now that it is used in directed super send trampolines. Use PushCq to pass small integer constants in the trampolines instead of smashing TempReg, which is now used to hold the directed supersend argument. Add support for PushCq. Could use PushCw but on x86 PushCq is a lot shorter. Mac builds: Use UTC as the timezone for the build timestamp. Using the local timezone doesn't work :(. -- best, Eliot

April 9, 2015

Re: [Pharo-dev] why we removed debugTest from nautilus?

by Marcus Denker

> On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Nicolai Hess wrote >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-… > > Ah, I miss that too! From that thread, it seems it was removed temporarily > until we have real breakpoints. Is there an issue for its return? > Not yet. Marcus

April 9, 2015