- Pharo-dev - lists.pharo.org

Pull Request for UpdatedPharoByExample
by Gaurav Singh April 1, 2015

April 1, 2015

Made changes in the Metaclasses chapter regarding syntax. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/5 Kindly review the pull request.

3 7

[pharo-project/pharo-core]
by GitHub April 1, 2015

April 1, 2015

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

1 0

[pharo-project/pharo-core] 39e425: 40591
by GitHub April 1, 2015

April 1, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 39e425ae36ecbbfbdc78b9fd51fac8c2917da57b https://github.com/pharo-project/pharo-core/commit/39e425ae36ecbbfbdc78b9fd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-01 (Wed, 01 Apr 2015) Changed paths: R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script590.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script591.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40590.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40591.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/PropertySlotTest.class/instance/tests/testRemovePropertySlot.st M Slot-Tests.package/PropertySlotTest.class/instance/tests/testRemovePropertySlot2.st A Slot.package/BaseSlot.class/README.md A Slot.package/BaseSlot.class/definition.st A Slot.package/BaseSlot.class/instance/initalize/default_.st A Slot.package/BaseSlot.class/instance/initalize/initialize_.st A Slot.package/BaseSlot.class/instance/meta-object-protocol/wantsInitalization.st A Slot.package/BaseSlot.class/instance/testing/isVisible.st R Slot.package/BooleanBaseSlot.class/README.md R Slot.package/BooleanBaseSlot.class/definition.st R Slot.package/BooleanBaseSlot.class/instance/initalize/initialize.st R Slot.package/BooleanBaseSlot.class/instance/initalize/initialize_.st R Slot.package/BooleanBaseSlot.class/instance/meta-object-protocol/wantsInitalization.st R Slot.package/BooleanBaseSlot.class/instance/testing/isVisible.st M Slot.package/BooleanSlot.class/instance/class building/layoutChanged_.st R Slot.package/PropertyBaseSlot.class/README.md R Slot.package/PropertyBaseSlot.class/definition.st R Slot.package/PropertyBaseSlot.class/instance/initalize/initialize.st R Slot.package/PropertyBaseSlot.class/instance/initalize/initialize_.st R Slot.package/PropertyBaseSlot.class/instance/meta-object-protocol/wantsInitalization.st R Slot.package/PropertyBaseSlot.class/instance/testing/isVisible.st M Slot.package/PropertySlot.class/instance/class building/layoutChanged_.st Log Message: ----------- 40591 15275 Small cleanup in Slot examples https://pharo.fogbugz.com/f/cases/15275 http://files.pharo.org/image/40/40591.zip

1 0

[ANN] New service: The Pharo catalog
by Esteban Lorenzano April 1, 2015

April 1, 2015

Hi, Last week I made a super small project to consolidate all projects published in all metarepos. Is very simple, in the style of smalltalkhub repository list, but it shows all projects with the info their owners provided. Yes, it could be a lot better, but we do not want to lose much time with this because not far in the future (but not right now) we will put online a much better service :) You can see the catalog here: http://catalog.pharo.org <http://catalog.pharo.org/> and a JSON variant here: http://catalog.pharo.org/catalog/json <http://catalog.pharo.org/catalog/json> enjoy, Esteban

6 8

[pharo-project/pharo-core]
by GitHub April 1, 2015

April 1, 2015

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

1 0

[pharo-project/pharo-core] 4805ad: 40590
by GitHub April 1, 2015

April 1, 2015

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4805add75116026600a454db57168d2d81514b30 https://github.com/pharo-project/pharo-core/commit/4805add75116026600a454db… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-01 (Wed, 01 Apr 2015) Changed paths: M MonticelloGUI.package/MCFileRepositoryInspector.class/definition.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/packageSelection_.st M MonticelloGUI.package/MCFileRepositoryInspector.class/instance/morphic ui/versionHighlightEmphasis_.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script589.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script590.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40589.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40590.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot-Tests.package/BooleanSlotTest.class/README.md A Slot-Tests.package/BooleanSlotTest.class/definition.st A Slot-Tests.package/BooleanSlotTest.class/instance/tests/testExampleBooleanSlot.st A Slot-Tests.package/BooleanSlotTest.class/instance/tests/testExampleTwoBooleanSlots.st A Slot.package/BooleanBaseSlot.class/README.md A Slot.package/BooleanBaseSlot.class/definition.st A Slot.package/BooleanBaseSlot.class/instance/initalize/initialize.st A Slot.package/BooleanBaseSlot.class/instance/initalize/initialize_.st A Slot.package/BooleanBaseSlot.class/instance/meta-object-protocol/wantsInitalization.st A Slot.package/BooleanBaseSlot.class/instance/testing/isVisible.st A Slot.package/BooleanSlot.class/README.md A Slot.package/BooleanSlot.class/definition.st A Slot.package/BooleanSlot.class/instance/TODO/todo.st A Slot.package/BooleanSlot.class/instance/class building/calculateOffset_.st A Slot.package/BooleanSlot.class/instance/class building/installingIn_.st A Slot.package/BooleanSlot.class/instance/class building/layoutChanged_.st A Slot.package/BooleanSlot.class/instance/meta-object-protocol/read_.st A Slot.package/BooleanSlot.class/instance/meta-object-protocol/write_to_.st Log Message: ----------- 40590 15269 a simple BooleanSlot example https://pharo.fogbugz.com/f/cases/15269 15234 monticello is not showing right status when working with branches https://pharo.fogbugz.com/f/cases/15234 http://files.pharo.org/image/40/40590.zip

1 0

SmalltalkHub is Exposing Email Addresses
by Sean P. DeNigris April 1, 2015

April 1, 2015

It would be better if they were hidden when the viewer is not logged in. ----- Cheers, Sean -- View this message in context: http://forum.world.st/SmalltalkHub-is-Exposing-Email-Addresses-tp4816531.ht… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 1

Moose Issue 1118: GT Inspector: Double Click Doesn't Always Select Text Properly
by Sean P. DeNigris March 31, 2015

March 31, 2015

https://code.google.com/p/moose-technology/issues/detail?id=1118 It took me a while to figure out that GT has a feature I've wanted for a long time: when you activate a workspace by clicking, the selection is preserved. Very cool! One thing though, where it also took me a while to figure out what was going on... 1. Type in the playground: 'aString'. 'anotherString'. 2. "Go" to bring up a second pane - doesn't matter which 3. Click in the second pane to put the keyboard focus there 4. Double click on one of the lines in pane #1 It is selected - great! 5. Repeat #3 6. Double click on the unselected line The selection will be cleared, but the other line will not be selected. NB: an interesting thing is that if you do the above exercise with a text editor outside the same GT window, like another GT Inspector, steps 5 and 6 work correctly just like the previous. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Moose-Issue-1118-GT-Inspector-Double-Click-Doesn-t-Al… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

1 0

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