March 2015 - Pharo-dev - lists.pharo.org

Issue regarding print block in the playground
by Gaurav Singh March 31, 2015

March 31, 2015

The print block in the Pharo 4.0 image playground sometimes seems to create problem. I have created a case in the issue tracker. Link : https://pharo.fogbugz.com/f/cases/15273/Issue-regarding-print-block-in-the-… , Can anyone look at the issue?

1 0

Re: [Pharo-dev] [squeak-dev] Bug whith contextOn:do:
by Eliot Miranda March 31, 2015

March 31, 2015

Hi Tobias, first let me sympathize. This is such horrible code :-(. Ovr the years, getting this code to work with Cog's context-to-stack-mapping machinery has given me headaches :-). On Tue, Mar 31, 2015 at 9:01 AM, Tobias Pape <Das.Linux(a)gmx.de> wrote: > Hey fellow Squeakers > > [Attention: low level lengthy stuff] > > I today encountered a strange behavior. > When running the Startup code, somewhen ContextPart>>#complete is called, > which, in the process issues #contextOn:do:, which subsequently somewhere > interanlly > does a jump: > > contextOn: exceptionClass do: block > "Create an #on:do: context that is ready to return from executing > its receiver" > > | ctxt chain | > ctxt := thisContext. > [chain := thisContext sender cut: ctxt. ctxt jump] on: > exceptionClass do: block. > "jump above will resume here without unwinding chain" > ^ chain > > The idea is that we end up right before '^ chain' as the comment indicates. > so what happens is that ctxt is the context of #contextOn:do: itself and > it gets > send #jump in the closure. > > Jump now does the following: > > jump > "Abandon thisContext and resume self instead (using the same > current process). You may want to save thisContext's sender before calling > this so you can jump back to it. > Self MUST BE a top context (ie. a suspended context or a abandoned > context that was jumped out of). A top context already has its return > value on its stack (see Interpreter>>primitiveSuspend and other suspending > primitives). > thisContext's sender is converted to a top context (by pushing a > nil return value on its stack) so it can be jump back to." > > | top | > "Make abandoned context a top context (has return value (nil)) so > it can be jumped back to" > thisContext sender push: nil. > > "Pop self return value then return it to self (since we jump to > self by returning to it)" > stackp = 0 ifTrue: [self stepToSendOrReturn]. > stackp = 0 ifTrue: [self push: nil]. "must be quick return > self/constant" > top := self pop. > thisContext privSender: self. > ^ top > > So. bytecode for #contextOn:do: is: > > 29 <8A 01> push: (Array new: 1) > 31 <6B> popIntoTemp: 3 > 32 <89> pushThisContext: > 33 <6A> popIntoTemp: 2 > 34 <12> pushTemp: 2 > 35 <13> pushTemp: 3 > 36 <8F 20 00 0A> closureNumCopied: 2 numArgs: 0 bytes 40 to 49 > 40 <89> pushThisContext: > 41 <D2> send: sender > 42 <10> pushTemp: 0 > 43 <E1> send: cut: > 44 <8E 00 01> popIntoTemp: 0 inVectorAt: 1 > 47 <10> pushTemp: 0 > 48 <D3> send: jump > 49 <7D> blockReturn > 50 <10> pushTemp: 0 > 51 <11> pushTemp: 1 > 52 <F0> send: on:do: > 53 <87> pop > 54 <8C 00 03> pushTemp: 0 inVectorAt: 3 > 57 <7C> returnTop > > > The jump lands right at 53 and does a pop. > HOWEVER, at this point the stack of this context is empty and the pop > actually pops the 3rd temp > from the temps that 'just happens' to be right under the stack. This > should be fatal. > HOWEVER again, Squeak actually does not pop but only decrement the SP so > the temp access still > works(this _could_ be fine but some implementations (Eg, RSqueak) tried > to separate temps and > stack; which is not possible currently). > > What could be the problem here? > - are the 'stackp = 0'-checks in #jump wrong and they actually should > check for the actual stack depth _after_ temps? > It does look like it. I would have expected this to be more correct: jump "Abandon thisContext and resume self instead (using the same current process). You may want to save thisContext's sender before calling this so you can jump back to it. Self MUST BE a top context (ie. a suspended context or a abandoned context that was jumped out of). A top context already has its return value on its stack (see Interpreter>>primitiveSuspend and other suspending primitives). thisContext's sender is converted to a top context (by pushing a nil return value on its stack) so it can be jump back to." | top | "Make abandoned context a top context (has return value (nil)) so it can be jumped back to" thisContext sender push: nil. "Pop self return value then return it to self (since we jump to self by returning to it)" stackp <= self numTemps ifTrue: [self stepToSendOrReturn]. (stackp <= self numTemps and: [self willJustPop]) ifTrue: [self push: nil]. "must be quick return self/constant" top := self pop. thisContext privSender: self. ^top > - should we put in a "sacrificial anode" in #contextOn:do: so that the pop > does not pop the empty stack? (like this: > > contextOn: exceptionClass do: block > "Create an #on:do: context that is ready to return from executing > its receiver" > > | ctxt chain | > ctxt := thisContext. > [chain := thisContext sender cut: ctxt. > ctxt push: nil. "sacrifical anode" > ctxt jump > ] on: exceptionClass do: block. > "jump above will resume here without unwinding chain" > ^ chain > That looks right. Once the on:do: is sent the thisContext of contextOn:do:'s stack contains only exceptionClass, block, context and the indirection vector containing chain. So it is in the stack = self numTemps case. > > - Or is there an even better way? > I'm not sure the other ways are any better. The way to transfer to a context without disturbing its stack is to do a process switch. So you do something equivalent to jump "Abandon thisContext and resume self instead (using the same current process)." | process semaphore | process := Processor activeProcess. semaphore := Semaphore new. [process suspendedContext unwindTo: self. process suspendedContext: self. semaphore signal] fork. semaphore wait This way no bizarre stack manipulations are going on, and no return value is pushed, because there isn't a return. One may get away with: jump "Abandon thisContext and resume self instead (using the same current process)." [| process | process := Processor activeProcess. process suspendedContext unwindTo: self. process suspendedContext: self] fork. Processor yield I'd be interested in your experience using either of these. One of the advantages the process switch versions have is in not updating the receiving context sp there's a chance the context-to-stack mapping machinery won't flush the context to the heap. In the end it might actually be faster. -- best, Eliot

1 0

Accessing pharo preferences directory
by Yuriy Tymchuk March 31, 2015

March 31, 2015

Hi, how do you access prefs dir? (The one that is ~/Library/Preferences/pharo/ on mac). Do you do (FileLocator preferences / #pharo) ensureCreateDirectory or there is a smarter way? Cheers. Uko

2 1

[pharo-project/pharo-core]
by GitHub March 31, 2015

March 31, 2015

Branch: refs/tags/40589 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] d42986: 40589
by GitHub March 31, 2015

March 31, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d4298600616020788d8fadef5660aa591d858904 https://github.com/pharo-project/pharo-core/commit/d4298600616020788d8fadef… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-31 (Tue, 31 Mar 2015) Changed paths: M Collections-Streams.package/Generator.class/README.md A Collections-Streams.package/Generator.class/class/examples/examplePrimes.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/browseVersions.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script588.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script589.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40588.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40589.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Slot.package/ExampleClassVariable.class/instance/as yet unclassified/read.st R Slot.package/ExampleClassVariable.class/instance/as yet unclassified/write_.st A Slot.package/ExampleClassVariable.class/instance/meta-object-protocol/read.st A Slot.package/ExampleClassVariable.class/instance/meta-object-protocol/write_.st R Slot.package/ExampleSlotWithDefaultValue.class/class/as yet unclassified/default_.st R Slot.package/ExampleSlotWithDefaultValue.class/instance/as yet unclassified/printOn_.st A Slot.package/ExampleSlotWithDefaultValue.class/instance/printing/printOn_.st Log Message: ----------- 40589 15268 Categorise some uncategorized methods in Slot examples https://pharo.fogbugz.com/f/cases/15268 15261 Generator: Move example from comment to method https://pharo.fogbugz.com/f/cases/15261 15266 browser version in nautilus without a method selected throws a DNU https://pharo.fogbugz.com/f/cases/15266 http://files.pharo.org/image/40/40589.zip

1 0

Listing Externally Maintained Packages
by Sean P. DeNigris March 31, 2015

March 31, 2015

Here's a useful snippet.. browseExternallyMaintainedPharoPackages <script> (RPackageOrganizer default packages select: [ :pkg | pkg mcPackage ifNotNil: [ :mcPkg | mcPkg remotes anySatisfy: [ :e | (MCRepositoryGroup default includes: e) not ] ] ifNil: [ false ] ]) inspect ----- Cheers, Sean -- View this message in context: http://forum.world.st/Listing-Externally-Maintained-Packages-tp4816401.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

MinimalConnectors/SmallUML port to Pharo 4.0
by Sean P. DeNigris March 31, 2015

March 31, 2015

I got them seeming to work and uploaded to http://smalltalkhub.com/mc/SeanDeNigris/SeansOutbox/main/ as I have access rights to neither repo. NB I temporarily changed the repo in the configs to the one above, so that will have to be changed if the package versions are copied to the canonical repo ----- Cheers, Sean -- View this message in context: http://forum.world.st/MinimalConnectors-SmallUML-port-to-Pharo-4-0-tp481615… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

5 14

Syslog client
by olivier auverlot March 31, 2015

March 31, 2015

Hi, I just released an UDP client for the Syslog network protocol (RFC5424). The product is available on SmalltalkHub. http://smalltalkhub.com/#!/~olivierauverlot/Syslog Best regards Olivier ;-)

4 4

[pharo-project/pharo-core]
by GitHub March 31, 2015

March 31, 2015

Branch: refs/tags/40588 Home: https://github.com/pharo-project/pharo-core

1 0

[pharo-project/pharo-core] 7f0802: 40588
by GitHub March 31, 2015

March 31, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7f08026b30bb5cece9204e157b8010043d84fbef https://github.com/pharo-project/pharo-core/commit/7f08026b30bb5cece9204e15… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-31 (Tue, 31 Mar 2015) Changed paths: M Nautilus.package/PackageTreeModel.class/instance/help-text/helpTextFor_.st M ProfStef-Core.package/PharoSyntaxTutorial.class/instance/lessons/theEnd.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script587.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script588.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40587.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40588.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M TxText-Athens.package/TxAthensLayoutView.class/instance/scrolling/scrollBy_.st Log Message: ----------- 40588 15253 URL to book in Tutorial is wrong https://pharo.fogbugz.com/f/cases/15253 14974 failing test testScrollToLargeX https://pharo.fogbugz.com/f/cases/14974 15241 Nautilus does not display catalogDescrption help text for many packages when moused over/clicked https://pharo.fogbugz.com/f/cases/15241 http://files.pharo.org/image/40/40588.zip

1 0