Re: [Pharo-dev] Would it be possible to also launch templates in PharoLauncher?

On 27 November 2017 at 10:08, Mariano Martinez Peck wrote: > Hi guys, > > Thank you Christophe for continue pushing this useful tool! > > One small request which might be easy to do... Quite frequently I want to do > something and re-save an image I have previosuly saved as

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

Hi, So you're advocating for solution 1: > > 1) We change the instVarAt: / instVarAt:put: primitives comments in Pharo > to match > the slotAt: / slotAt:put: primitives behavior I marked in bold the changes in the Pharo comment (so the comment now reflects the actual behavior): instVarAt:

Re: [Pharo-dev] Would it be possible to also launch templates in PharoLauncher?

On Sun, Nov 26, 2017 at 11:08 PM, Mariano Martinez Peck < marianop...@gmail.com> wrote: > Hi guys, > > Thank you Christophe for continue pushing this useful tool! > > One small request which might be easy to do... Quite frequently I want to > do something and re-save an image I have previosuly

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

On Mon, Nov 27, 2017 at 12:11:13PM -0800, Eliot Miranda wrote: > Hi Cl??ment, > > On Wed, Nov 22, 2017 at 5:35 AM, Cl??ment Bera > wrote: > > > Hi All, > > > > It seems Pharo is lacking the slotAt: / slotAt:put: primitive and that the > > instVarAt: / instVarAt:put:

[Pharo-dev] QA rule suggestion - assignment symbol slips

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.

[Pharo-dev] [Pharo 7.0-dev] Build #343: 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest, ...

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:

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

--- Begin Message --- Marcus, I agree with keeping it as Slot. The existing literature (non-Smalltalk) uses Slot in a fairly consistent manner so what would the advantage be of changing it? Reg Sent from my iPhone > On Nov 24, 2017, at 4:44 AM, Clément Bera wrote: >

Re: [Pharo-dev] [Pharo 7.0-dev] Build #332: 20759 Unused temps in Metacello classes

Yes - I submitted a PR to Metacello too: https://github.com/Metacello/metacello/pull/473 Who is able to merge it there? > Gesendet: Montag, 27. November 2017 um 09:16 Uhr > Von: "Marcus Denker" > An: "Pharo Development List" > Betreff: Re:

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

Hi Clément, On Wed, Nov 22, 2017 at 5:35 AM, Clément Bera wrote: > 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

[Pharo-dev] [Pharo 7.0-dev] Build #342: 20745-cleanup-unused-methods-OCOptimizedBlockScope

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:

[Pharo-dev] [Pharo 7.0-dev] Build #341: 20700-translateToUTC-does-not-work-on-Month-and-Year

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:

[Pharo-dev] [Pharo 7.0-dev] Build #340: 20770-Open-WelcomeHelp-window-at-startup

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

[Pharo-dev] [Pharo 7.0-dev] Build #339: 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone

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:

[Pharo-dev] [Pharo 7.0-dev] Build #338: 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone

There is a new Pharo build available! The status of the build #338 was: FAILURE. 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:

[Pharo-dev] [Pharo 7.0-dev] Build #337: 19304-anyOne-comment-should-be-improved

There is a new Pharo build available! The status of the build #337 was: SUCCESS. The Pull Request #552 was integrated: "19304-anyOne-comment-should-be-improved" Pull request url: https://github.com/pharo-project/pharo/pull/552 Issue Url: https://pharo.fogbugz.com/f/cases/19304 Build

Re: [Pharo-dev] Is SmalltalkCI working for Pharo projects?

Fabio fixed it. Aliaksei please try restarting your failing builds. On Sun, Nov 26, 2017 at 11:13 AM, Aliaksei Syrel wrote: > Hi, > > We have the same problem. It infinitly loops on coverage and says "out of > memory" in the end. > > Cheers, > Alex > > On Nov 26, 2017 2:18

[Pharo-dev] [Pharo 7.0-dev] Build #336: 20768-remove-GLMWatcherMorphicTest

There is a new Pharo build available! The status of the build #336 was: SUCCESS. The Pull Request #551 was integrated: "20768-remove-GLMWatcherMorphicTest" Pull request url: https://github.com/pharo-project/pharo/pull/551 Issue Url: https://pharo.fogbugz.com/f/cases/20768 Build Url:

[Pharo-dev] [Pharo 7.0-dev] Build #335: 20758-Slot-should-have-explicit-property-definingClass2

There is a new Pharo build available! The status of the build #335 was: SUCCESS. The Pull Request #543 was integrated: "20758-Slot-should-have-explicit-property-definingClass2" Pull request url: https://github.com/pharo-project/pharo/pull/543 Issue Url:

Re: [Pharo-dev] clarifying pharo crashing issue(s)

On 27-11-17 12:08, Tudor Girba wrote: How do they crash? When you run something specific? Different things. The script crashed reliably on all my machines the last time I checked. Stephan

Re: [Pharo-dev] clarifying pharo crashing issue(s)

Hi, How do they crash? When you run something specific? Doru > On Nov 27, 2017, at 11:56 AM, stephan wrote: > > On 27-11-17 09:20, Tudor Girba wrote: >> Hi, >> There are recurrent reports that Pharo is crashing often. >> So, first question: >> - is Pharo crashing on another

[Pharo-dev] [Pharo 7.0-dev] Build #334: 20766-Increase-priority-of-FreeType-initialization

There is a new Pharo build available! The status of the build #334 was: SUCCESS. The Pull Request #548 was integrated: "20766-Increase-priority-of-FreeType-initialization" Pull request url: https://github.com/pharo-project/pharo/pull/548 Issue Url:

Re: [Pharo-dev] clarifying pharo crashing issue(s)

On 27-11-17 09:20, Tudor Girba wrote: Hi, There are recurrent reports that Pharo is crashing often. So, first question: - is Pharo crashing on another system than MacOS Sierra or HighSierra? Yes, older MacOS, Ubuntu 16.04LTS, Windows 7 & 10. Both 64 and 32 bit, latest and stable vms. I'm

Re: [Pharo-dev] clarifying pharo crashing issue(s)

2017-11-27 9:38 GMT+01:00 Norbert Hartl : > It is even crashing headless. I have one jenkins job where the build fails > everytime because the vm is crashing. 32 bit runs fine > Yes: my headless image building makefiles would segfault. Thierry > > Norbert > > Am

[Pharo-dev] [Pharo 7.0-dev] Build #333: 20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI-

There is a new Pharo build available! The status of the build #333 was: SUCCESS. The Pull Request #508 was integrated: "20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI-" Pull request url: https://github.com/pharo-project/pharo/pull/508 Issue Url:

Re: [Pharo-dev] Iceberg operations overview

On 22-11-17 09:33, Pavel Krivanek wrote: during brainstorming of the Iceberg UI simplification we created a document that shows what the current Iceberg operations do. It should help you to clarify the role of the working copy etc. Thanks, that is helpful. From the discussions on discord and

Re: [Pharo-dev] clarifying pharo crashing issue(s)

It is even crashing headless. I have one jenkins job where the build fails everytime because the vm is crashing. 32 bit runs fine Norbert > Am 27.11.2017 um 09:34 schrieb Thierry Goubier : > > > > 2017-11-27 9:20 GMT+01:00 Tudor Girba : >> Hi,

Re: [Pharo-dev] clarifying pharo crashing issue(s)

2017-11-27 9:20 GMT+01:00 Tudor Girba : > 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. > >

Re: [Pharo-dev] Linux vm packages

I can edit the website, I can put al needed infos there. (but sometimes I am not be able to generate actions out of discussions on the mailing list, there is just so much going on… so if something does not happen this just means I do not know that it should happen…) > On 26 Nov 2017, at

[Pharo-dev] clarifying pharo crashing issue(s)

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

Re: [Pharo-dev] [Pharo 7.0-dev] Build #332: 20759 Unused temps in Metacello classes

This fix has been submitted upstream, too. > On 27 Nov 2017, at 09:09, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #332 was: SUCCESS. > > The Pull Request #546 was integrated: "20759 Unused temps in Metacello > classes" >

[Pharo-dev] [Pharo 7.0-dev] Build #332: 20759 Unused temps in Metacello classes

There is a new Pharo build available! The status of the build #332 was: SUCCESS. The Pull Request #546 was integrated: "20759 Unused temps in Metacello classes" Pull request url: https://github.com/pharo-project/pharo/pull/546 Issue Url: https://pharo.fogbugz.com/f/cases/20759 Build