- Pharo-dev - lists.pharo.org

Iceberg "Create repository" buttons
by Ben Coman Nov. 28, 2017

Nov. 28, 2017

In Iceberg I am finding the "Create repository" button disconcerting for some of the Iceberg repository dialogs. For example, clicking "Add local repository" shows a dialog "Import local repository into Iceberg" with a "Create repository" button and perception of this which I can't shake is "Whoa! I don't want to create a repository. It already exists!" Perhaps this is a narrow view, but for me a git repository exists properly on a remote or under the ".git" folder on the file system. Repositories don't exist inside the Image, only a single checked out working version. So "Create repository" feels like it can only operating on the file system. This is a left-brain/right-brain thing. Technically I can reason its the only button so pushing it can't be wrong, but it "feels" like pushing it will do the wrong thing. wdyt? cheers -ben

1 0

[Pharo 7.0-dev] Build #344: 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest, ...
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2017

Nov. 28, 2017

There is a new Pharo build available! The status of the build #344 was: SUCCESS. The Pull Request #557 was integrated: "20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,..." Pull request url: https://github.com/pharo-project/pharo/pull/557 Issue Url: https://pharo.fogbugz.com/f/cases/20772 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

QA rule suggestion - assignment symbol slips
by Ben Coman Nov. 28, 2017

Nov. 28, 2017

A quick suggestion for anyone working on QA rules... Just now I am playing with FFI a bit and switching back a forth from Pharo to C and sometimes I end up doing... location = Libclang clang_getRangeStart__range: range. thus QA reported a. "Temporaries read before written" and b. "Temporary variables not read or not written" but these weren't helpful since I was stuck staring at it saying to myself "Well range is assigned before its used, and location is assigned, so bah! the rules seem broken" and for about 30 seconds I remained blind to the truth I'd left the colon off the assignment operator. I'd expect newcomers from other languages might slip in the same way, so a higher priority rule extending [b.] that identifies such variable followed by equal-sign would provide pertinent feedback. cheers -ben

2 4

clarifying pharo crashing issue(s)
by Tudor Girba Nov. 28, 2017

Nov. 28, 2017

Hi, There are recurrent reports that Pharo is crashing often. However, at the moment I believe the reasons are not clarified. So, this mail is not about fixing the issues, but first about clarifying what they are. Namely: - I know about the typing problem on MacOS (Sierra or High Sierra). I encounter this problem daily (literally), and I know that I am not the only one. For example, this can occur when I type âclasssâ fast and then delete the last character. It is documented here: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/141 - Some people talk about the FreeType problem, but I could not find a place where this is described. So, while this might be a problem, I am not sure that this problem is actually causing crashes. So, first question: - is Pharo crashing on another system than MacOS Sierra or HighSierra? - how does the FreeType problem look like? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

5 7

Problem with primitive instVarAt: / instVarAt:put:, what should we do ?
by ClÃ©ment Bera Nov. 28, 2017

Nov. 28, 2017

Hi All, It seems Pharo is lacking the slotAt: / slotAt:put: primitive and that the instVarAt: / instVarAt:put: primitive is not doing what it says it does. When I look at Object>>#instVarAt: I see: "[...]Answer a fixed variable in an object. The numbering of the variables corresponds to the named instance variables, followed by the indexed instance variables. Fail if the index is not an Integer or is not the index of a fixed variable[...]" Now in Pharo 7 when one does: #(iv1) instVarAt: 1, one gets #iv1. So the comment is wrong. The reason for this is that instVarAt: / instVarAt:put: should be primitive 73/74, while they are in Pharo 173/174 (primitive slotAt:/slotAt:put:). The slot primitive access pointer slots of objects, whichever inst var or variable fields. A good example would be: | t | t := #temp. [ t ] instVarAt: 4, one gets #temp So I have two solutions for this problem: 1) We change the instVarAt: / instVarAt:put: primitives comments to match the slotAt: / slotAt:put: behavior, and in Pharo instVarAt: / instVarAt:put: means in factslotAt: / slotAt:put: . 2) We change the instVarAt: / instVarAt:put: primitives to primitive 73 and 74, we introduce slotAt: / slotAt:put: with primitive 173/174 and we ask everyone to fix their code relying on instVarAt: / instVarAt:put: acting as slotAt: / slotAt:put: What do you think ? Best, -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

7 13

[Pharo 7.0-dev] Build #343: 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest, ...
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #343 was: FAILURE. The Pull Request #557 was integrated: "20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,..." Pull request url: https://github.com/pharo-project/pharo/pull/557 Issue Url: https://pharo.fogbugz.com/f/cases/20772 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #342: 20745-cleanup-unused-methods-OCOptimizedBlockScope
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #342 was: SUCCESS. The Pull Request #556 was integrated: "20745-cleanup-unused-methods-OCOptimizedBlockScope" Pull request url: https://github.com/pharo-project/pharo/pull/556 Issue Url: https://pharo.fogbugz.com/f/cases/20745 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #341: 20700-translateToUTC-does-not-work-on-Month-and-Year
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #341 was: SUCCESS. The Pull Request #545 was integrated: "20700-translateToUTC-does-not-work-on-Month-and-Year" Pull request url: https://github.com/pharo-project/pharo/pull/545 Issue Url: https://pharo.fogbugz.com/f/cases/20700 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #340: 20770-Open-WelcomeHelp-window-at-startup
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #340 was: SUCCESS. The Pull Request #555 was integrated: "20770-Open-WelcomeHelp-window-at-startup" Pull request url: https://github.com/pharo-project/pharo/pull/555 Issue Url: https://pharo.fogbugz.com/f/cases/20770 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #339: 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2017

Nov. 27, 2017

There is a new Pharo build available! The status of the build #339 was: SUCCESS. The Pull Request #553 was integrated: "20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone" Pull request url: https://github.com/pharo-project/pharo/pull/553 Issue Url: https://pharo.fogbugz.com/f/cases/20769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0