- Pharo-dev - lists.pharo.org

Hackathon IoT. I used Pharo.
by phil＠highoctane.be Feb. 24, 2016

Feb. 24, 2016

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

6 11

New Cog VMs available
by Eliot Miranda Feb. 24, 2016

Feb. 24, 2016

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3630 a.k.a. http://www.mirandabanda.org/files/Cog/VM/latest. Noe tat there is a JIT bug in the 64-bit VMs which I shall look at this week. CogVM binaries as per VMMaker.oscog-eem.1697/r3630 General: Fix serious bug in jitted perform: primitive. Thanks to Stephane Ducasse for finding and to Levente Uzoni for diagnosing the bug. If the argument count is one greater than the max number of register arguments (2 in Spur, hence perform:with:with:) then the code to remove the receiver and arguments from the stack neglects to remove the receiver and selector. Spur: Fix bug in markAndTraceWeaklingsFrom:. Fields of weaklings may be immediate so must use followOopField:ofObject: not followObjField:ofObject:. Fix https://pharo.fogbugz.com/f/cases/17536/VM-Crash-when-adding-an-iVar-to-a-s… . When weaklings (and when ephemerons) are scan-marked forwarders must be coped with. 64-bit VMs: Fix a bug in printHex: for 64-bits (faulty arithmetic). ThreadedFFIPlugin: Fix the remaining 64-bit issues in the ThreadedFFIPlugin. The X64SysVFFIPlugin now passes the test suite. Hence include the FFI plugin in 64-bit VMs. Mac VMs: Have the Mac OS X build install Localizable.strings. Add versions for Newspeak, Pharo and Squeak. Rename the key to SelectImagePanePrompt. Temporarily disable the Serial plugin in the Pharo Mac VM until we can track down the relevant platforms/iOS support for the Pharo extensions. Fix argument access on the iOS platform (Mac OS VMs). _,,,^..^,,,_ best, Eliot

1 0

Problem loading new class comments
by Sven Van Caekenberghe Feb. 23, 2016

Feb. 23, 2016

I am working on https://pharo.fogbugz.com/f/cases/16893/Update-STON and I noticed that class comments did not update, even if they are changed. Specifically, the class comments of ConfigurationOfSton and STONWriter did definitively change, I can see the changed comments in the MC code browser, but when I load the code, the comments stay the same, both in Nautilus as using the #comment message. #50591 Sven

3 4

nautilus does not refresh method changed
by stepharo Feb. 23, 2016

Feb. 23, 2016

Hi may be this is already fixed but in Latest update: #50596 I found myself forced to reopen a class to see its correct method. Stef

1 0

fully self-contained Linux VM
by Peter UhnÃ¡k Feb. 23, 2016

Feb. 23, 2016

Hi, is it possible to have fully self-contained Linux VM? Right now if you want to use Pharo on Linux you have to install some libraries directly in the system, which isn't particularly user-friendly. I know that for example libcairo (needed by Roassal) has hard-coded library paths, but maybe this can be changed so the library can be in the zip. Could something like that be done also for the remaining lib32 libraries required to run the VM? Even if it had to be a special bundle for each linux distribution. Thanks, Peter

6 6

curiousity, ensure unwind block priority inheritance
by Ben Coman Feb. 23, 2016

Feb. 23, 2016

Just thought I'd share something enlightening I learnt today, a curious surprise... When a process is terminated, the #ensure: unwind block effectively inherits the priority of the terminator process. Thus the following... log := OrderedCollection new. s := Semaphore new. p := [ [ log add: 1. s signal. log add: 4. ] ensure: [log add: 5] ] forkAt: 30. s wait. log add: 2. "p terminate." log add: 3. 100 milliSeconds wait. Transcript crShow: log. ...gives {1 2 3 4 5} as expected. However uncommenting the terminate statement produces {1 2 5 3}. Quite non-intuitive** to have the "5" code inside the priority 30 block execute before the "3" code of the priority 40 of the UI/Playground. **meaning it bit me for a few hours trying to understand some ProcessTests related to Case 17588. cheers -ben

1 0

[pharo-project/pharo-core]
by GitHub Feb. 23, 2016

Feb. 23, 2016

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

1 0

[pharo-project/pharo-core] a8609c: 50603
by GitHub Feb. 23, 2016

Feb. 23, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a8609c784255b249c46006004e78a224022e4e8d https://github.com/pharo-project/pharo-core/commit/a8609c784255b249c4600600… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-23 (Tue, 23 Feb 2016) Changed paths: R Deprecated50.package/extension/SmalltalkImage/instance/addToShutDownList_.st R Deprecated50.package/extension/SmalltalkImage/instance/addToStartUpList_.st M SUnit-UITesting.package/SimulateKeystrokesSpecification.class/instance/tests/testSimulateCmdKeystroke.st M SUnit-UITesting.package/SimulateMouseSpecification.class/instance/tests/testSimulateRightClick.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50602.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50603.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50602.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50603.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Support.package/SmalltalkImage.class/instance/startup - shutdown/addToShutDownList_.st A System-Support.package/SmalltalkImage.class/instance/startup - shutdown/addToStartUpList_.st Log Message: ----------- 50603 17676 Building Pharo-5.0-Issue-Tracker-Image fails!! https://pharo.fogbugz.com/f/cases/17676 16534 SimulateMouseSpecification broken https://pharo.fogbugz.com/f/cases/16534 http://files.pharo.org/image/50/50603.zip

1 0

Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point>
by Esteban Lorenzano Feb. 23, 2016

Feb. 23, 2016

> On 23 Feb 2016, at 13:20, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Alain Plantec <alain.plantec(a)yahoo.com> > Subject: Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point> > Date: 23 February 2016 at 13:19:34 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello Doru, > >> On 23 Feb 2016, at 10:33, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> At the moment, it is used for documentation purposes in Bloc. It is part of the effort of Alex to document Bloc thoroughly. I think it is an interesting idea, in that we would have a significant case study for that can be used later as optional types information to improve static tool support. And it does not hurt at the moment. >> >> What do you think? > > Experimenting optional types is a good idea. We could have Tools to dynamically check them. > What about a separate typing model that could be used to add/remove the types annotations ? > Also, I wonder if Bloc is the good package to experiment optional types. Maybe it is not stable enough. > Cheers > Alain please, please, please keep the scope of those experiments aside the main effort who is to have Block/Brick running as soon as possible. Esteban ps: â¦ optional typesâ¦ at the end, we will realise Gilad was right all this time :) > > >> >> Cheers, >> Doru >> >> >>> On Feb 23, 2016, at 10:25 AM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>> >>> >>> From: Alain Plantec <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>> >>> Subject: Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point> >>> Date: February 23, 2016 at 10:23:33 AM GMT+1 >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> >>> >>> >>> I donât like it too. >>> Alain >>> >>>> Le 23 fÃ©vr. 2016 Ã 09:50, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> a Ã©crit : >>>> >>>> >>>> >>>> 2016-02-23 9:47 GMT+01:00 stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>>: >>>> Hi >>>> >>>> I saw that something <return: #Point> or <return: Point> >>>> I do not know why but I have the impression that <return: #Point> is better. >>>> Because we may have code not present and still want to load the code. >>>> >>>> I would like to know for what this is used. >>>> I don't like it. >>>> >>>> >>>> Stef >>>> >>>> >>> >>> >>> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "We are all great at making mistakes." > > >

3 3

[pharo-project/pharo-core]
by GitHub Feb. 23, 2016

Feb. 23, 2016

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

1 0