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

font bug status check (I need feedback)

by Esteban Lorenzano

Soâ¦ Iâm reviewing https://pharo.fogbugz.com/f/cases/17392/ Since last two fixes we made last week, Iâm not capable to find it anymoreâ¦ so, Iâm looking for feedbackâ¦ please? :) cheers, Esteban

March 24, 2016

Re: [Pharo-dev] Pharo Days 2016 @ end of next week

by Stephan Eggermont

On 24-03-16 11:13, Sven Van Caekenberghe wrote: > If you really want to pay another way, just opt for the invoice/pay > afterwards option, and I'll send you an invoice and you can then pay > by bank transfer. Sven Done. Stephan

March 24, 2016

Re: [Pharo-dev] Pharo Days 2016 @ end of next week

by Sven Van Caekenberghe

> On 24 Mar 2016, at 11:08, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 24-03-16 10:46, Sven Van Caekenberghe wrote: >> Much can be said about what happened this week >> >> https://en.wikipedia.org/wiki/2016_Brussels_bombings >> >> but basically most people are just very, very sad > Indeed > >> The Pharo Days 2016 take place at the end of next week, as planned. We already >> have 25 confirmed registrations. Please consider joining us. Registrations close >> at the beginning of next week (Tuesday March 29th, midnight). We urge you to >> please register as soon as possible. >> > > Payment doesn't work from the Netherlands. It tries to force me to create a > paypal account. I believe that is indeed the only option (although, I thought at least, that you do not really have to create an account, that you can do just a payment through them, but that option is probably well hidden, or maybe gone). If you really want to pay another way, just opt for the invoice/pay afterwards option, and I'll send you an invoice and you can then pay by bank transfer. Sven

March 24, 2016

[pharo-project/pharo-core]

by GitHub

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

March 24, 2016

[pharo-project/pharo-core] 08a1a0: 50659

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 08a1a07549088f5591d225a8574900f57761d9f9 https://github.com/pharo-project/pharo-core/commit/08a1a07549088f5591d225a8… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-24 (Thu, 24 Mar 2016) Changed paths: M Collections-Tests.package/StringTest.class/instance/requirements/sortedInAscendingOrderCollection.st A Collections-Tests.package/StringTest.class/instance/testing/testFindStringStartingAtCaseSensitive.st A Collections-Tests.package/StringTest.class/instance/testing/testFindTokens.st A Collections-Tests.package/StringTest.class/instance/testing/testFindTokensEscapedBy.st A Collections-Tests.package/StringTest.class/instance/testing/testFindTokensIncludes.st A Collections-Tests.package/StringTest.class/instance/testing/testFindWordStartStartingAt.st A Collections-Tests.package/StringTest.class/instance/testing/testHasWideCharacterFromTo.st A Collections-Tests.package/StringTest.class/instance/testing/testIncludesSubstring.st A Collections-Tests.package/StringTest.class/instance/testing/testIncludesSubstringCaseSensitive.st A Collections-Tests.package/StringTest.class/instance/testing/testIndexOf.st A Collections-Tests.package/StringTest.class/instance/testing/testIndexOfFirstUppercaseCharacter.st A Collections-Tests.package/StringTest.class/instance/testing/testIndexOfWideCharacterFromTo.st A Collections-Tests.package/StringTest.class/instance/testing/testInitialIntegerOrNil.st A Collections-Tests.package/StringTest.class/instance/testing/testIsAllAlphaNumerics.st A Collections-Tests.package/StringTest.class/instance/testing/testIsWideString.st A Collections-Tests.package/StringTest.class/instance/testing/testLastSpacePosition.st A Collections-Tests.package/StringTest.class/instance/testing/testLeadingCharRunLengthAt.st A Collections-Tests.package/StringTest.class/instance/testing/testNumericSuffix.st A Collections-Tests.package/StringTest.class/instance/testing/testOccursInWithEmptyCaseSensitive.st A Collections-Tests.package/StringTest.class/instance/testing/testOnlyLetters.st A Collections-Tests.package/StringTest.class/instance/testing/testTranslateToLowercase.st A Collections-Tests.package/StringTest.class/instance/testing/testTranslateToUppercase.st R Collections-Tests.package/StringTest.class/instance/tests - indexof/testIndexOf.st M Kernel.package/Context.class/instance/private/doPrimitive_method_receiver_args_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50658.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50659.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50658.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50659.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50659 17872 simulation mirror primitive100 for perform with superclass is not working https://pharo.fogbugz.com/f/cases/17872 17873 Simple Test Cases for String (continued) https://pharo.fogbugz.com/f/cases/17873 http://files.pharo.org/image/50/50659.zip

March 24, 2016

Re: [Pharo-dev] Pharo Days 2016 @ end of next week

by Stephan Eggermont

On 24-03-16 10:46, Sven Van Caekenberghe wrote: > Much can be said about what happened this week > > https://en.wikipedia.org/wiki/2016_Brussels_bombings > > but basically most people are just very, very sad Indeed > The Pharo Days 2016 take place at the end of next week, as planned. We already > have 25 confirmed registrations. Please consider joining us. Registrations close > at the beginning of next week (Tuesday March 29th, midnight). We urge you to > please register as soon as possible. > Payment doesn't work from the Netherlands. It tries to force me to create a paypal account. Stephan

March 24, 2016

Pharo Days 2016 @ end of next week

by Sven Van Caekenberghe

Much can be said about what happened this week https://en.wikipedia.org/wiki/2016_Brussels_bombings but basically most people are just very, very sad An international community working together on open source software as a common good that can benefit anyone anywhere is one of those things that can make a difference, that can show how living together should be. The Pharo Days 2016 take place at the end of next week, as planned. We already have 25 confirmed registrations. Please consider joining us. Registrations close at the beginning of next week (Tuesday March 29th, midnight). We urge you to please register as soon as possible. http://pharodays2016.pharo.org We hope to see you all soon ! The Pharo Board

March 24, 2016

Re: [Pharo-dev] modifying copied context vars

by Henrik Nergaard

Not only is the test failing, but if you modify line 13 from â(1 to: 2) do: â to â(1 to: 1) do:â in #doTestDebuggerTempAccessWith:with: then Pharo will crash post spur, while pre spur the last assertion will fail. Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess Sent: Thursday, March 24, 2016 9:53 AM To: Pharo Development List <pharo-dev(a)lists.pharo.org>; The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Subject: [Pharo-dev] modifying copied context vars Hello, we have a failing test (OCClosureCompilerTest>>#testDebuggerTempAccess) (fails since spur, but not related - I think). A simple example to reproduce the behavior: | local1 remote1| remote1:=4. local1 :=3. [:i | |c| c := local1. remote1 := i. i halt. "local1:=25. <-- evaluate during debugging" ] value:1. Transcript show:local1;cr. Transcript show:remote1;cr. (Executing this code and evaluating "local:=25" after the debugger halts for "i halt" will modify the var "remote1" instead of "local1", as this is a vector tempvar , proceeding the execution will crash at accessing the remote1 value). The purpose of the testDebuggerTempAccess test case is, evaluating code that changes the value of a copied temp var *does not* change the value of this var in the outer context. (see comment in the test case: "this is not 25 as the var is a local, non escaping variable that was copied into the block, If the compiler would have known about the write, it would have made the var escaping". ) But the implementation (OCCopyingTempVariable>>#writeFromContext: aContext scope: contextScope value: aValue) explicitly iterates through all outer context(s) and changes the vars as well. 1. Question: Who is right? But the reason why the test actually fails is different. It is because evaluating the code that modifies the var "local1:=25" ends up to a call aContext tempAt: self indexFromIR put: aValue but the index (indexFromIR) can be different for every context (method context / inner block context(s)). 2. Question: should the index be always the same? thanks inadvance Nicolai ps: since spur (resp. compiler changes that were done for new spur images), the index of tempvars can be different. In pre-spur, this testcase modifies an outer context var, but one that isn't checked (the argument "two"), therefore the test succeed. In spur, this testcase modifes a different outer context var "remote1", and the test fails.

March 24, 2016

modifying copied context vars

by Nicolai Hess

Hello, we have a failing test (OCClosureCompilerTest>>#testDebuggerTempAccess) (fails since spur, but not related - I think). A simple example to reproduce the behavior: | local1 remote1| remote1:=4. local1 :=3.[:i | |c| c := local1. remote1 := i. i halt. "local1:=25. <-- evaluate during debugging" ] value:1. Transcript show:local1;cr. Transcript show:remote1;cr. (Executing this code and evaluating "local:=25" after the debugger halts for "i halt" will modify the var "remote1" instead of "local1", as this is a vector tempvar , proceeding the execution will crash at accessing the remote1 value). The purpose of the testDebuggerTempAccess test case is, evaluating code that changes the value of a copied temp var *does not* change the value of this var in the outer context. (see comment in the test case: "this is not 25 as the var is a local, non escaping variable that was copied into the block, If the compiler would have known about the write, it would have made the var escaping". ) But the implementation (OCCopyingTempVariable>>#writeFromContext: aContext scope: contextScope value: aValue) explicitly iterates through all outer context(s) and changes the vars as well. 1. Question: Who is right? But the reason why the test actually fails is different. It is because evaluating the code that modifies the var "local1:=25" ends up to a call aContext tempAt: self indexFromIR put: aValue but the index (indexFromIR) can be different for every context (method context / inner block context(s)). 2. Question: should the index be always the same? thanks inadvance Nicolai ps: since spur (resp. compiler changes that were done for new spur images), the index of tempvars can be different. In pre-spur, this testcase modifies an outer context var, but one that isn't checked (the argument "two"), therefore the test succeed. In spur, this testcase modifes a different outer context var "remote1", and the test fails.

March 24, 2016

Re: [Pharo-dev] Discussing FileSystem >> #workingDirectory and VM process getcwd(3)

by Dale Henrichs

I think it was a shell command and`sudo` may have been required ... I had to do it with Mavericks (or earlier) ... it's possible that with Yosemite that it is no longer possible:) I haven't checked for a while. Dale On 3/23/16 5:46 PM, Eliot Miranda wrote: > Hi Dale, > > On Tue, Mar 22, 2016 at 7:49 AM, Dale Henrichs > <dale.henrichs(a)gemtalksystems.com > <mailto:dale.henrichs@gemtalksystems.com>> wrote: > > Mariano, > > I think this _is_ the OSX issue that I was talking about ... there > is a way to arrange for PWD to be set correctly when double > clicking apps, but it has to be set a system option so each user > has to do it themselves ... > > > Is that a setting in the Desktop preferences (or...?) or is it a > setting on the app itself? > > > > Dale > > > On 3/22/16 6:01 AM, Mariano Martinez Peck wrote: >> >> >> On Tue, Mar 22, 2016 at 9:37 AM, Damien Pollet >> <damien.pollet(a)gmail.com <mailto:damien.pollet@gmail.com>> wrote: >> >> Because there is this concept called "consistency" that's >> interesting to have :p >> >> If your code wants $HOME it can ask for it explicitly, same >> for /. However if it just wants to do something in $PWD >> consistent with most use-cases, the image directory is the >> sensible default. >> >> >> I agree with Pollet. I don't care if it is image directory or >> $HOME. What I care is that $PWD of the VM process should match >> with FileSystem >> workingDirectory. And right now it does not >> match. >> >> >> On 22 March 2016 at 13:05, Damien Cassou >> <damien.cassou(a)inria.fr <mailto:damien.cassou@inria.fr>> wrote: >> >> Damien Pollet <damien.pollet(a)gmail.com >> <mailto:damien.pollet@gmail.com>> writes: >> >> > On 22 March 2016 at 12:56, Damien Cassou >> <damien.cassou(a)inria.fr <mailto:damien.cassou@inria.fr>> >> wrote: >> > >> >> typical applications ran with double-click are bound >> to the HOME >> >> directory. Why do you want to do it differently? >> >> >> > >> > Only on Linux. On OS X it's / >> >> so, why do you want to make it the image directory? >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another >> without >> losing enthusiasm." --Winston Churchill >> >> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com > > > > > -- > _,,,^..^,,,_ > best, Eliot

March 24, 2016