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

[pharo-project/pharo-core]

by GitHub

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

Feb. 22, 2016

[pharo-project/pharo-core] ec7c45: 50598

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: ec7c457d58d271bff6b6aa58c97b6c790a6fa17a https://github.com/pharo-project/pharo-core/commit/ec7c457d58d271bff6b6aa58… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-22 (Mon, 22 Feb 2016) Changed paths: M Collections-Strings.package/Symbol.class/class/private/initSelectorTable.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testModulePrimitive.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50597.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50598.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50597.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50598.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50598 17650 testModulePrimitive: fix test for new byte codes https://pharo.fogbugz.com/f/cases/17650 17629 OCContextTempMappingTest tests fails on Spur Images https://pharo.fogbugz.com/f/cases/17629 17015 Failing test: SetTest>>#testAllSetsAreHealthy https://pharo.fogbugz.com/f/cases/17015 http://files.pharo.org/image/50/50598.zip

Feb. 22, 2016

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

by philippe.back＠highoctane.be

LoRa stuff with sensors etc. Integrated REST apis for that in Pharo. I'll do a writeup on my blog. Lots of opportunities for Pharo in that space. Phil On Feb 22, 2016 2:49 PM, "Serge Stinckwich" <serge.stinckwich(a)gmail.com> wrote: > Great ! What did you exactly, I'm interested by details ;-) > > 2016-02-22 14:42 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > > > http://geeko.lesoir.be/2016/02/22/hackapost-un-hackathon-sur-les-applis-iot… > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

Feb. 22, 2016

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

by Serge Stinckwich

Great ! What did you exactly, I'm interested by details ;-) 2016-02-22 14:42 GMT+01:00 phil(a)highoctane.be <phil(a)highoctane.be>: > http://geeko.lesoir.be/2016/02/22/hackapost-un-hackathon-sur-les-applis-iot… -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 22, 2016

Re: [Pharo-dev] Smalltalkhub scheduled maintenance today (February, 22nd)

by Stephan Eggermont

On 22-02-16 13:42, Christophe Demarey wrote: > Smalltalkhub is now back on line! Thanks for taking care! Stephan

Feb. 22, 2016

Hackathon IoT. I used Pharo.

by phil＠highoctane.be

http://geeko.lesoir.be/2016/02/22/hackapost-un-hackathon-sur-les-applis-iot…

Feb. 22, 2016

Re: [Pharo-dev] Any download statistics for Pharo

by Marcus Denker

> On 20 Feb 2016, at 11:15, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Hi, > > do we have any download statistics for Pharo? > > No. Marcus

Feb. 22, 2016

Re: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules

by Sven Van Caekenberghe

> On 20 Feb 2016, at 12:34, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > > Ah, test testMetaclass. Somehow I only read testClass.... > > Moving those two methods from Metaclass to TApplyingOnClassSide should make the test happy. Well, that looked strange at first, but I studied it a bit further and you are most probably right. I decided to move the methods. Thx > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe > Sent: Saturday, February 20, 2016 11:58 AM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules > > If I add (in #50591) my methods to the exception set in the middle, the test is green > > self > assert: > (Metaclass localSelectors difference: ClassTrait localSelectors) > = > {#externalTypeAlias:. > #baseClass. > #basicLocalSelectors:. > #basicLocalSelectors. > #classClass. > #isClass. > #stonName. "<<<" > #stonOn:. "<<<" > #environment. > #fileOutOn:. > #fileOutOn:initializing:. > #postCopy. > #traitComposition. > #traitComposition:. > #veryDeepCopyWith:} asSet. > > I don't know about the other failures. > >> On 20 Feb 2016, at 11:37, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: >> >> The issue should be unrelated: >> >> https://pharo.fogbugz.com/f/cases/17616/CI-Server-Failing-tests-related-to-… >> >> Best regards, >> Henrik >> >> -----Original Message----- >> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe >> Sent: Saturday, February 20, 2016 11:05 AM >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules >> >> Hi, >> >> I am trying to load a new version of STON in Pharo 5 >> >> https://pharo.fogbugz.com/f/cases/16893/Update-STON >> >> One of the tests that fails is MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules >> >> More specifically, (Metaclass localSelectors difference: ClassTrait localSelectors) is no longer equal to the exceptions defined in the test because #stonName and #stonOn: were added to Metaclass >> >> What should I do ? Did I do something wrong ? >> >> Should I add to the exceptions defined in the test or should I add them to ClassTrait ? >> >> I think the first sounds the most correct. >> >> Thx, >> >> Sven >> >> > > >

Feb. 22, 2016

Re: [Pharo-dev] Yet again, wrong tempvars in debuggers context variables list

by Marcus Denker

> On 22 Feb 2016, at 10:27, Guille Polito <guillermopolito(a)gmail.com> wrote: > > Hmm, I know that the Spur bootstrap does a lot of changes "in the background". For example, it replaces literals in methods (Float->BoxedFloat64), plus it inlines all immediate characters. > > I do not know if it is related, but this could be a side effect, and it would explain why there is no evident change causing this. > We should have recompiled the whole image afterâ¦ lets do this soon and see. > > On 02/22/2016 09:08 AM, Nicolai Hess wrote: >> >> >> 2016-02-20 20:31 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com> <mailto:nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>>>: >> >> >> >> 2016-02-20 19:11 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com> >> <mailto:nicolaihess@gmail.com <mailto:nicolaihess@gmail.com>>>: >> >> This is not an issue with GTDebugger, but the way opal >> generates the tempvar >> index or the way, debuggerMap tries to access the context vars >> >> 17660 >> <https://pharo.fogbugz.com/f/cases/17660/wrong-tempvar-values-in-debugger <https://pharo.fogbugz.com/f/cases/17660/wrong-tempvar-values-in-debugger>> >> wrong tempvar values in debugger >> >> >> This is a really special case, I wasn't able yet to create an >> easier example for reproducing this bug: >> - put a self haltOnce in >> RAbstractClass>>#directlyDefinesLocalMethod: >> - enable halt once >> - select any other method in Nautilus and choose >> "Rename method (all)" from method panes context menu >> - enter a new name and push "OK" >> -> the debugger pops up in method >> directlyDefinesLocalMethod: >> - select the first "allClassesDo:" context from top of the stack >> -> the debugger shows that we are in the evalBlock context >> The "seen" variable is a Set, but if you look at the >> "Variables"-pane, it is shown >> as a block (this is actually the parameter aBlock) >> >> >> again, this is caused by a change for spur migration >> >> This worked up to pharo 50496 >> starting with pharo 50497, the order of variables has changed. >> >> see >> http://forum.world.st/pharo-project-pharo-core-dfd4f3-50497-td4867046.html <http://forum.world.st/pharo-project-pharo-core-dfd4f3-50497-td4867046.html> >> <https://pharo.fogbugz.com/f/cases/17241/ffi-nb-is-not-cleaning-compiled-met… <https://pharo.fogbugz.com/f/cases/17241/ffi-nb-is-not-cleaning-compiled-met…>> >> >> >> Any idea what has changed? >> I could not spot a change that could be responsible for this. >> The order of tempvars in a block context somehow changed, and the way the debugger accesses the temps >> by name (get an index and access the context temp vars by index) somehow changed. >> Recompiling the affected methods helps, but I would like to know if this change (where is it?) was on purpose.

Feb. 22, 2016

Re: [Pharo-dev] [Pharo-users] Who is using Pharo Launcher and for what

by Damien Cassou

Tudor Girba <tudor(a)tudorgirba.com> writes: > I use it for writing documentation and blog posts. what is the relationship between Pharo Launcher and your documentation and blog posts? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 22, 2016