- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Feb. 13, 2017

Feb. 13, 2017

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

1 0

RGMethodDefinition>>gtInspectorSourceIn: does not refresh on <accept>
by Ben Coman Feb. 13, 2017

Feb. 13, 2017

Anyone know if the following bug has been logged previously? I've had a quick search and not found anything. 1. #hierarchyButtonAction: inspect 2. Select [Implementors] tab. 3. Select [Source tab] 4. Edit method, the yellow dirty mark shows in the corner 5. Accept edit e.g. <Ctrl-S> ==> nothing seems to happen. The method still shows dirty, ==> but if you select [Senders] tab and back to [Source] tab ==> you see the method *was* saved. cheers -ben P.S. Its really cool to be able to edit the method here. I'm using halos to dive into a PluggableToggleButtonMorph (e.g. <Hier>) then selecting the actionSelector > Implementors > Source and insert a halt.

1 0

Esteban's ChangeLog week of 6 February 2017
by estebanlm＠gmail.com Feb. 13, 2017

Feb. 13, 2017

Hello! This is my weekly ChangeLog, from 6 February 2017 to 12 February 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=6/2/2017&to=12/2/2017 ChangeLog ========= 9 February 2017: ---------------- * I finished the work started yesterday and now there is a [Pull Request](https://github.com/npasserini/iceberg/pull/276) enabling the use of SSH for iceberg :) 8 February 2017: ---------------- * I worked with Pablo on *iceberg*, in [issue 275](https://github.com/npasserini/iceberg/issues/275) (enable use of ssh-agent). It is very important to provide an easy way to use the tool (otherwise you need to provide your username/password, and there is people who do not like this). After one afternoon of hard work, we now have an "almost" working version, as you can see [here](https://github.com/estebanlm/iceberg/commits/dev-0.4) This thing in fact should be working, but there are still some UI missing stuff and it is not validated on other platforms (linux and windows)... ut it 'should' work... we'll see tomorrow :) 7 February 2017: ---------------- * I'm working on restore the testing of VM builds, and so far linux tests are passing. There are some problems in macOS (probably due to missing chunks when performing the merge), and windows is still not tested at all. So, I will work tomorrow on those to see if we can have finished the process this week: I need to have a stable VM to continue with iceberg development (users will need to have a new VM, so better to have it tested :P) 6 February 2017: ---------------- * Working a bit on VM, I integrated a [pull request](https://github.com/pharo-project/pharo-vm/pull/114) that will enhance the build process in linux platforms. This was submited by [Holger](https://github.com/zecke), and is part of his work to create VM package versions. cheers! Esteban

2 1

Nice library looking for clever developers for little chat and lovely documentation
by stepharong Feb. 12, 2017

Feb. 12, 2017

Hi guys I realized that value: valueWithPossibleArguments: cull: and others supernice messages do not have the method comments they deserved. cull: anArg ^numArgs = 0 ifTrue: [self value] ifFalse: [self value: anArg] => I started https://pharo.fogbugz.com/f/cases/19689/Add-method-comments-to-cool-block-m… cull: anArg "Execute the receiver with one or zero arguments depending on the receiver number of required arguments." "([ 12 ] cull: 13) >>> 12 " "([:x | x + 12] cull: 3) >>> 15 " ^numArgs = 0 ifTrue: [self value] ifFalse: [self value: anArg] Any takers? because it would be really nice to say to newcomers that our core libraries are super cool. Stef

1 0

Context stack semantics (was Re: GTDebugger variables table)
by Ben Coman Feb. 12, 2017

Feb. 12, 2017

On Fri, Feb 3, 2017 at 11:33 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, Feb 3, 2017 at 10:21 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >> Or maybe it [Stack] would be better as a tab of thisContext's next pane. >> > > Actually you can try this now... > > Context>>stackValueMap > | stackValues stackDepth| > stackValues := OrderedCollection new. > stackDepth := self basicSize min: 21. > (stackDepth to: 1 by: -1) do: [ :index | > |key| > key := (index = stackDepth) ifTrue: ['Top'] ifFalse: [(stackDepth - index + > 1) asString]. > stackValues add: (key -> (self basicAt: index)) > ]. > ^stackValues > > Context>>gtInspectorStackValuesIn: composite > <gtInspectorPresentationOrder: 40> > | stackValues | > stackValues := self stackValues. > ^ (composite table) > title: 'Stack'; > display: [ self stackValueMap ]; > column: 'Depth' evaluated: [ :assoc | assoc key ] width: 50; > column: 'Item' evaluated: [ :assoc | GTObjectPrinter new > asTruncatedTextFrom: assoc value ] > > > I'm not sure whether the #stackValueMap is an appropriate name. Perhaps it > should be #methodStackValueMap or something else? Similar for the tab name. A couple of times already I've missed not having this in fresh Images. Since its simple and low impact I hoping to add it for Pharo 6, but I'd like to check the semantics are right As a comparison, what I understand of C lang is it has only one stack (per thread) for: * execution flow return to caller's next statement * function parameters * function local variables So C kind of combines call stack and variable stack.. In Pharo, the top pane of the debugger shows a stack of Contexts as returned by "thisContext stack" which is effectively is for * execution flow return to caller's next statement And from what I learnt writing #stackValueMap above it seems , that each Context has its own stack for: * function parameters * function local variables * calculations / parameter marshalling for message sends So how should the second stack be referred to? Any of the following? * methodStackValues? * contextStackValues? * valueStack? * stackValues? and btw I wonder if Context>>stack would be better named Context>>callStack Here is my current refinement of the methods... Context>>stackValues | stackValues stackDepth| stackValues := OrderedCollection new. stackDepth := self basicSize min: 21. (stackDepth to: 1 by: -1) do: [ :index | stackValues add: (self basicAt: index) ]. ^stackValues Context>>composite <gtInspectorPresentationOrder: 30> |stackValues| stackValues := self stackValues. ^ composite table title: 'Value Stack'; display: [ :aCollection | [(1 to: stackValues size) collect: [ :index | index -> (stackValues at: index) ]] on:Error do:[#()]]; beMultiple; column: 'Index' evaluated: [ :assoc | (assoc key = 1 ifTrue: ['Top'] ifFalse: [ assoc key asString ])] width: 50; column: 'Item' evaluated: [ :assoc | GTObjectPrinter new asTruncatedTextFrom: assoc value ]; send: [ :result | result isNil ifTrue: [ nil ] ifFalse: [ result value size = 1 ifTrue: [result anyOne value] ifFalse: [self species withAll: (result collect: [:each | each value])]]]; showOnly: 50 cheers -ben

1 0

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 11, 2017

Feb. 11, 2017

Hi all, I've managed to get all information from the System report browser. I'll attach it to this email. Surprisingly (at least for me), Pharo doesn't crash if I execute it like the following: strace -f ./pharo-ui Pharo.image (before this, I executed it without -f). So, I'm attaching also part of the output from the command execution. strace generates a lot of such log messages like you can see in the log file strace-f-pharo.log (something is wrong, but I'm not sure what exactly is wrong). Best regards, Andriy.

1 0

[pharo-project/pharo-core] fcd75f: 60386
by GitHub Feb. 11, 2017

Feb. 11, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: fcd75f0830aa6925f2fee68011ae20fb30efee81 https://github.com/pharo-project/pharo-core/commit/fcd75f0830aa6925f2fee680… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-11 (Sat, 11 Feb 2017) Changed paths: R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60385.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60386.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60385.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60386.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-FileList.package/FileList.class/instance/accessing/contents.st A Tool-FileList.package/FileList.class/instance/accessing/getEncoding.st M Tool-FileList.package/FileList.class/instance/file menu action/getHex.st A Tool-FileList.package/FileList.class/instance/private/knownEncodingIdentifiers.st M Tool-FileList.package/FileList.class/instance/private/readContentsBrief_.st M Tool-FileList.package/FileList.class/instance/private/readContentsHex_.st M Tool-FileList.package/FileList.class/instance/private/selectEncoding.st A Tool-FileList.package/FileList.class/instance/private/streamFirst5000BytesFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFirst5000BytesWithEncodingFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFullContentsFrom_.st A Tool-FileList.package/FileList.class/instance/private/streamFullContentsWithEncodingFrom_.st Log Message: ----------- 60386 18778 FileList "View as" does not work https://pharo.fogbugz.com/f/cases/18778 http://files.pharo.org/image/60/60386.zip

2 1

[pharo-project/pharo-core]
by GitHub Feb. 11, 2017

Feb. 11, 2017

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

1 0

Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted
by Stephane Ducasse Feb. 10, 2017

Feb. 10, 2017

https://pharo.fogbugz.com/f/cases/19661/When-coding-in-the-debugger-I-get-a… Then I got a really strange problem when I was doing the counter execise using the debugger. create a Test Case TestCase subclass: #CounterTest instanceVariableNames: '' classVariableNames: '' package: 'Counter' - add testValueAtCreation self assert: (Counter new count: 10) count equals: 10 - ok to define classes - define count: in the class Counter - count: anInteger count := anInteger - Declare instance variable count NOW problem Instance of class did not understand count - ok to define it => Instance of IRMethod do not understand sourceNodeExecuted HAnging around instances ========== Then if I remove the Counter class and relaunch the tests I get Instance of anObsoleteCounter did not understandâ¦.

3 2

Re: [Pharo-dev] Segmentation fault while installing Scale
by Andrey Tykhonov Feb. 10, 2017

Feb. 10, 2017

Hello, > Hi, > We are looking at it with Santi. I see in the log that you're using an ubuntu 12? No, this is Gentoo Linux. > I tried in a debian jessie and Santi in an ubuntu 14 and we could not > reproduce it. Also the travis ci of scale uses ubuntu 12 and the > installation works in there... > Could you give more details about your system? Sure, but I'm not sure which exactly information will be useful, so, please clarify. For now, I'm sending you kernel version: $ uname -a Linux tp 4.9.6-gentoo #1 SMP Thu Jan 26 17:04:47 EET 2017 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz GenuineIntel GNU/Linux > Thanks, Guille and Santi Thank you! -- Andriy

1 0