- Pharo-dev - lists.pharo.org

Latest Pharo 70 linux VM is itimer?

by Alistair Grant

Hi Everyone, Downloading the latest 7.0 linux VM with: curl get.pharo.org/vmLatest70 | bash on linux gives a itimer VM: $ ./pharo --version 5.0-201802171019 Sat Feb 17 10:27:09 UTC 2018 gcc 4.8.4 [Production Spur ITHB VM] CoInterpreter VMMaker.oscog-eem.2320 uuid: e2692e35-5fc8-4623-95d0-b445b3329f75 Feb 17 2018 StackToRegisterMappingCogit VMMaker.oscog-eem.2324 uuid: 904abc56-e5a8-467e-a337-880211e33805 Feb 17 2018 VM: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sat Feb 17 11:19:01 2018 +0100 $ Plugins: 201802171019 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux travis-job-cc93cae9-4623-4046-bc51-1d5e0f1daa41 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 i686 i686 i686 GNU/Linux plugin path: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019 [default: /tmp/p7vm/pharo-vm/lib/pharo/5.0-201802171019/] My understanding is that this should be threaded heartbeat. Can someone clarify what's happening? Thanks! Alistair

Feb. 20, 2018

[JOB][Research] 3 Year Starting Research Positions

by Marcus Denker

Inria opended a call for starting researchers. This is a three year contract. REQUIREMENTS - Have a French doctorate or an equivalent international degree - From 2 to 8 years of experience in research (after the thesis) - No age or nationality conditions. - Deadline: April 3rd, 2018 Before writing their research program, the applicants are strongly encouraged to contact the teams or project(s)-teams leaders concerned by their applications. More information on the official website: https://www.inria.fr/en/institute/recruitment/offers/starting-research-posi… MISSION Join one of our two lines of research: Tools for Software Maintenance or New Programming Language Constructs for Software Evolution. THE REGION Lille is strategically located in Northern Europe with train connections to Paris (1h), London (1h30) and Brussels (30 min.) The Nord Pas de Calais region is a dynamic area in both industry and research for computer science with companies that are european leaders in their branch. Lille, the capital of northern France is an attractive metropolis of over 1 million inhabitants. Cost of living in Lille is lower than that of very big cities such as Paris and London. THE TEAM RMoD is an Inria research project team. It consists of 5 permant researchers (Inria CR and DR, as well as University Assistant Professors) and Engineers, postdocs and students (Master and PhD). RMoD is an international team with more than 20 members from six countries. LINKS: RMoD: http://rmod.lille.inria.fr INRIA Lille: http://www.inria.fr/lille/ INRIA in General: http://www.inria.fr Lille: http://en.wikipedia.org/wiki/Lille http://wikitravel.org/en/Lille Please contact the head of the research team: Stephane.Ducasse(a)inria.fr or one of the following group members: Nicolas.Anquetil(a)inria.fr, Marcus.Denker(a)inria.fr Permanent Link: https://rmod.inria.fr/web/blog/2018-02-19

Feb. 20, 2018

[ANN] Pharo Sprint Feb 23

by Marcus Denker

Pharo Sprint Feb 23 https://association.pharo.org/event-2789568 For a list of all future Pharo Event, have a look at: https://association.pharo.org/events (you can get iCal entries and subsribe to an event specific mailinglist bu registering) Marcus

Feb. 20, 2018

Re: [Pharo-dev] NeoCSV nil-Handling

by Sven Van Caekenberghe

Sean, > On 19 Feb 2018, at 02:33, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sven Van Caekenberghe-2 wrote >> What do you think ? > > Could #emptyFieldValue: accept a block instead of the actual value? Or be > per-field? Or both? Then the default could still be set via the current > mechanism, keeping the usual API simple, but the user would have a bit more > control. Have a look at the following: === Name: Neo-CSV-Core-SvenVanCaekenberghe.27 Author: SvenVanCaekenberghe Time: 19 February 2018, 10:28:24.688684 pm UUID: a08d6c1c-f921-0d00-aaa4-29b9044088b7 Ancestors: Neo-CSV-Core-SvenVanCaekenberghe.26 Add special option #passNil for NeoCSVReader>>#emptyFieldValue: so that converter blocks do get nil passed in for empty/missing fields and can act accordingly Add NeoCSVReaderTests>>#testEmptyFieldValuePassNil === Name: Neo-CSV-Tests-SvenVanCaekenberghe.24 Author: SvenVanCaekenberghe Time: 19 February 2018, 10:28:03.52381 pm UUID: 1598291b-f921-0d00-aaa3-c7c0044088b7 Ancestors: Neo-CSV-Tests-SvenVanCaekenberghe.23 Add special option #passNil for NeoCSVReader>>#emptyFieldValue: so that converter blocks do get nil passed in for empty/missing fields and can act accordingly Add NeoCSVReaderTests>>#testEmptyFieldValuePassNil === Now you can do as follows: | date1 date2 | date1 := '1900-01-01' asDate. date2 := '2000-12-31' asDate. self assert: ((NeoCSVReader on: 'date1,date2\2018-01-01,2018-02-01\2018-01-01,\,2018-02-01\\' withCRs readStream) emptyFieldValue: #passNil; addFieldConverter: [ :input | input ifNil: [ date1 ] ifNotNil: [ input asDate ] ]; addFieldConverter: [ :input | input ifNil: [ date2 ] ifNotNil: [ input asDate ] ]; skipHeader; upToEnd) equals: (Array with: (Array with: '2018-01-01' asDate with: '2018-02-01' asDate) with: (Array with: '2018-01-01' asDate with: date2) with: (Array with: date1 with: '2018-02-01' asDate) with: (Array with: date1 with: date2)). Note how the first field's default empty value is now date1 and second field's is date2. Sven

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Ah, sorry, yes #valueWithArguments: does throw errors. Best regards Stefan > On 19 Feb 2018, at 20:17, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > > Hi Mariano: > >> On 19 Feb 2018, at 20:09, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> >> I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. > > Did you try my examples? > I donât think this is correct. > In Pharo 6.1, #valueWithArguments: doesnât throw any errors as far as I can see. It inserts nil for absent arguments however. > > This is what I tried: > > blocks := { > [ { } ]. > [:a | { a } ]. > [:a :b | { a. b } ]. > [:a :b :c | { a. b. c } ] > }. > > blocks collect: [:b | b valueWithPossibleArgs: {1}]. > blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. > blocks collect: [:b | b valueWithEnoughArguments: {1}]. > blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. > > > Best regards > Stefan > > > -- > Stefan Marr > School of Computing, University of Kent > http://stefan-marr.de/research/ > > -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Hi Mariano: > On 19 Feb 2018, at 20:09, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. Did you try my examples? I donât think this is correct. In Pharo 6.1, #valueWithArguments: doesnât throw any errors as far as I can see. It inserts nil for absent arguments however. This is what I tried: blocks := { [ { } ]. [:a | { a } ]. [:a :b | { a. b } ]. [:a :b :c | { a. b. c } ] }. blocks collect: [:b | b valueWithPossibleArgs: {1}]. blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. blocks collect: [:b | b valueWithEnoughArguments: {1}]. blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. Best regards Stefan -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 19, 2018

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Mariano Martinez Peck

On Fri, Feb 16, 2018 at 2:25 PM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > I am trying to understand the different between and perhaps origin of > BlockClosure>>#valueWithPossibleArgs: and BlockClosure>># > valueWithEnoughArguments: > > I am trying to decide which of the two I need for SOMns. > > The first one has seen more recent changes, when looking at the Pharo 6.1 > download: > > valueWithPossibleArgs: anArray â> 2/12/2017 StephaneDucasse > valueWithEnoughArguments: anArray â> 3/11/2001 nk > > While they have rather different implementations, they seem to behave > identically, as far as I could tell using the following example: > > blocks := { > [ { } ]. > [:a | { a } ]. > [:a :b | { a. b } ]. > [:a :b :c | { a. b. c } ] > }. > > blocks collect: [:b | b valueWithPossibleArgs: {1}]. > blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. > blocks collect: [:b | b valueWithEnoughArguments: {1}]. > blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. > > I was also wondering how they relate to #cull:* > > One of the major differences seems to be that valueWithP* and valueWithE* > are both injecting nil for absent arguments, while normal #value* and > #cull* methods signal an error. > Is there a specific use case why one wouldnât want to be strict here as > well, but instead inject nils? > I guess it's because we offer both flavors. If you see valueWithArguments: you will see it does throw errors like #value* / #cull* do. > Any comments or pointer appreciated. > > Thanks > Stefan > > > -- > Stefan Marr > School of Computing, University of Kent > http://stefan-marr.de/research/ > > > > -- Mariano http://marianopeck.wordpress.com

Feb. 19, 2018

[ANN] ba-st Web Stack new versions available

by Gabriel Cotelli

Hi, We're happy to announce a new version of the Web Stack hosted at https://github.com/ba-st/. This is a multi-release announcement of the following related project versions: - Willow <https://github.com/ba-st/Willow> v6.0.0. Changes since latest announcement: - Added interaction on document load - Improved temporarily disabling command - Added identification support to unordered lists - Improved new location opening commands - Improved interaction fuctions to always include the event as a parameter - Improved asynchronic links to auto-configure a script doing preventDefault - Refactored the link support - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v6.0.0 - Updated Willow base support to v6.0.0 - Improved Split Button support to allow triggering actions on the main button only - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v5.0.0 - Updated Willow base support to v6.0.0 - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v3.0.0 - Updated Willow base support to v6.0.0 - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v2.0.0 - Updated dependencies to the latest versions - RenoirSt <https://github.com/ba-st/RenoirSt> v4.0.0 - Removed Pharo 4 support - Updated dependencies SemanticUI <https://github.com/ba-st/Willow-SemanticUI> integration is still a work in progress. There's a new Materialize CSS <https://github.com/fortizpenaloza/Willow-Materialize> integration being worked on by Francisco Ortiz. Find a more detailed changelog and migration instructions on the release pages of each repository. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed, and you can also start following our new tech blog @ mercap <https://medium.com/mercap-tech-blog> for Smalltalk and Pharo related posts and experience reports. Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

Feb. 19, 2018

[Pharo 7.0-dev] Build #578: 21373-Fix-Tests-Failing-after-Change-in-Examples

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #578 was: SUCCESS. The Pull Request #916 was integrated: "21373-Fix-Tests-Failing-after-Change-in-Examples" Pull request url: https://github.com/pharo-project/pharo/pull/916 Issue Url: https://pharo.fogbugz.com/f/cases/21373 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 19, 2018

Re: [Pharo-dev] Iceberg 0.6.8 backported to 6.1

by Sean P. DeNigris

Sean P. DeNigris wrote > FYI #60530 is supposed to have Iceberg 0.6.8, but there is something > amiss. Any progress on this? I'm a bit stuck because I already started porting my baselines to use `gitlab://` ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2018