January 2017 - Pharo-dev - lists.pharo.org

AST node replacement API

by Yuriy Tymchuk

Hi everyone, does anyone have a better knowledge about replacing nodes in AST? Because what I saw is that there are methods like replaceSourceWith: that can be sent to an AST node with another AST node as a parameter. But this is not enough to get a new source code. Because when you ask the AST for newSource it generates a new source by taking replacements into account, parses the new source, compares it with itself and in case the new parse tree is equal it returns the new source. So itâs not enough to just use replaceSourceWith: but you also have to replace the current node with a new one it AST. Now the question is: am I doing something wrong, or we have strange API because we need to replace both source and node, replacing only one of them does not workâ¦ Uko

Jan. 23, 2017

Re: [Pharo-dev] [Pharo6] Issue tracker: Issues tagged Pharo6

by denker

I will check with Esteban this week for a plan with real datesâ¦ > On 23 Jan 2017, at 12:38, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > When is the release planned? > > Peter > > On Mon, Jan 23, 2017 at 11:58:19AM +0100, Marcus Denker wrote: >> Hi, >> >> To be able to release, we have to check which issues are real show-stoppers. >> >> As a first step, we will, this Friday, remove the Pharo6 Milestone tag from *all* >> issues that are priority âwould be niceâ or lower. >> >> https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i… <https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i…> >> >> These are 281 issues right now. >> >> It would be nice if everyone would look at the issues that they have been involved in an adjust priority of needed. >> >> Marcus >

Jan. 23, 2017

[pharo-project/pharo-core]

by GitHub

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

Jan. 23, 2017

[pharo-project/pharo-core] 87ff0d: 60352

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 87ff0de86204c116f3c523414a8b704dbae15097 https://github.com/pharo-project/pharo-core/commit/87ff0de86204c116f3c52341… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-01-23 (Mon, 23 Jan 2017) Changed paths: M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st M Kernel.package/ProtoObject.class/instance/comparing/~~.st M Polymorph-Widgets.package/ThemeIcons.class/class/accessing/baseUrl.st M Polymorph-Widgets.package/ThemeIcons.class/instance/private/defaultUrl.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60351.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60352.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60351.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60352.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60352 19554 #~~ should be a primitive and a compile-time inlined selector to be consistent with #== https://pharo.fogbugz.com/f/cases/19554 19573 more rigid ThemeIcons defaultUrl https://pharo.fogbugz.com/f/cases/19573 http://files.pharo.org/image/60/60352.zip

Jan. 23, 2017

Re: [Pharo-dev] AioPlugin not present

by Thierry Goubier

2017-01-23 12:57 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 23 Jan 2017, at 12:46, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > 2017-01-23 12:40 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 23 Jan 2017, at 12:37, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> >> >> >> 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> >>> me neither :) >>> I added AioPlugin (as external) to all linux distributionsâ¦ they will be >>> available in latest VMs. >>> >>> can someone test it? >>> >> >> I'll try. Where is the source for the current pharo vms? On github, >> pharo-vm? >> >> >> https://github.com/pharo-project/pharo-vm >> > > Thanks. > > How do you build a 64bits linux vm? The doc is limited to 32 bits. > > > README is not updated, and process is not like that anymore. > Now, you have to go do: > > cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build (for threaded) > cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build.itimerheartbeat > (for itimer) > > then just ./mvm > And you reply y / n to the clean? question in the mvm script? Regards, Thierry > > cheers, > Esteban > > > Regards, > > Thierry > > >> >> cheers, >> Esteban >> >> >> I'd like to try building it, to see if my 64bits issues would be solved. >> >> Thierry >> >> >>> >>> Esteban >>> >>> > >>> > Whatever the reason for that, the notifier about the missing plugin was >>> > too annoying, so I got rid of it in the latest OSProcess update: >>> > >>> > Name: OSProcess-Base-dtl.56 >>> > Time: 17 January 2017, 8:47:36.321587 am >>> > >>> > OSProcess 4.6.7 >>> > >>> > Add nil checks in #shutDown: to prevent failures when exiting existing >>> > image with a VM that does not include OSPP (e.g. SqueakJS). >>> > >>> > For AIO event hander, if the AIO plugin is not present, write an error >>> > to console rather than interrupting the image with a notifer. Reduces >>> the >>> > annoyance level if VM provider provides OSPP but neglects to include >>> the >>> > AIO plugin. >>> > >>> > Dave >>> > >>> > >>> >> >

Jan. 23, 2017

Re: [Pharo-dev] Pharo by Example 50 released!

by Dimitris Chloupis

Since you mention this, in case of any beginners following this list please note that even though we try to make PBE as beginner friendly as possible still it is not. There is still a lot of work needed to be done to lay down the basics of Pharo. Also the focus of the book is not just beginners but rather to be a very lengthy tutorial for anything contained inside Pharo. For example even the original PBE had chapters on TDD Metaprogramming Reflection Streams and many other non beginner friendly/orientated subjects I hope the generic nature of the book will be kept and not be turned into "Pharo for dummies book" which would take a ton of work anyway. So even if you consider yourself an experienced Pharo developer, please take a look and help us improve it. On Mon, Jan 23, 2017 at 12:01 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. > > This is a great entry point into Pharo. > > Please publicize it as widely as you can. Here is the announcement tweet > that you can retweet: > https://twitter.com/stephaneducasse/status/823195882770284545 > > Cheers, > Doru > > > On Jan 22, 2017, at 4:53 PM, stepharong <stepharong(a)free.fr> wrote: > > > > > https://pharoweekly.wordpress.com/2017/01/22/pharo-by-example-50-released/ > > > > Super special thanks to Nicolai Hess that pushed me to do the last steps > to release. > > Thanks Nicolai your steady commits pushed me! > > > > Stef > > > > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving should be focused on describing > the problem in a way that makes the solution obvious." > > > > > > >

Jan. 23, 2017

Re: [Pharo-dev] AioPlugin not present

by Esteban Lorenzano

> On 23 Jan 2017, at 12:46, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2017-01-23 12:40 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 23 Jan 2017, at 12:37, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> >> >> 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >> >> me neither :) >> I added AioPlugin (as external) to all linux distributionsâ¦ they will be available in latest VMs. >> >> can someone test it? >> >> I'll try. Where is the source for the current pharo vms? On github, pharo-vm? > > https://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > > Thanks. > > How do you build a 64bits linux vm? The doc is limited to 32 bits. README is not updated, and process is not like that anymore. Now, you have to go do: cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build (for threaded) cd opensmalltalk-vm/build.linux64x64/pharo.cog.spur/build.itimerheartbeat (for itimer) then just ./mvm cheers, Esteban > > Regards, > > Thierry > > > cheers, > Esteban > >> >> I'd like to try building it, to see if my 64bits issues would be solved. >> >> Thierry >> >> >> Esteban >> >> > >> > Whatever the reason for that, the notifier about the missing plugin was >> > too annoying, so I got rid of it in the latest OSProcess update: >> > >> > Name: OSProcess-Base-dtl.56 >> > Time: 17 January 2017, 8:47:36.321587 am >> > >> > OSProcess 4.6.7 >> > >> > Add nil checks in #shutDown: to prevent failures when exiting existing >> > image with a VM that does not include OSPP (e.g. SqueakJS). >> > >> > For AIO event hander, if the AIO plugin is not present, write an error >> > to console rather than interrupting the image with a notifer. Reduces the >> > annoyance level if VM provider provides OSPP but neglects to include the >> > AIO plugin. >> > >> > Dave >> > >> >

Jan. 23, 2017

Re: [Pharo-dev] AioPlugin not present

by Thierry Goubier

2017-01-23 12:40 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 23 Jan 2017, at 12:37, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> >> me neither :) >> I added AioPlugin (as external) to all linux distributionsâ¦ they will be >> available in latest VMs. >> >> can someone test it? >> > > I'll try. Where is the source for the current pharo vms? On github, > pharo-vm? > > > https://github.com/pharo-project/pharo-vm > Thanks. How do you build a 64bits linux vm? The doc is limited to 32 bits. Regards, Thierry > > cheers, > Esteban > > > I'd like to try building it, to see if my 64bits issues would be solved. > > Thierry > > >> >> Esteban >> >> > >> > Whatever the reason for that, the notifier about the missing plugin was >> > too annoying, so I got rid of it in the latest OSProcess update: >> > >> > Name: OSProcess-Base-dtl.56 >> > Time: 17 January 2017, 8:47:36.321587 am >> > >> > OSProcess 4.6.7 >> > >> > Add nil checks in #shutDown: to prevent failures when exiting existing >> > image with a VM that does not include OSPP (e.g. SqueakJS). >> > >> > For AIO event hander, if the AIO plugin is not present, write an error >> > to console rather than interrupting the image with a notifer. Reduces >> the >> > annoyance level if VM provider provides OSPP but neglects to include >> the >> > AIO plugin. >> > >> > Dave >> > >> > >> >> >> > >

Jan. 23, 2017

Re: [Pharo-dev] AioPlugin not present

by Esteban Lorenzano

> On 23 Jan 2017, at 12:37, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2017-01-23 12:26 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > > > me neither :) > I added AioPlugin (as external) to all linux distributionsâ¦ they will be available in latest VMs. > > can someone test it? > > I'll try. Where is the source for the current pharo vms? On github, pharo-vm? https://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> cheers, Esteban > > I'd like to try building it, to see if my 64bits issues would be solved. > > Thierry > > > Esteban > > > > > Whatever the reason for that, the notifier about the missing plugin was > > too annoying, so I got rid of it in the latest OSProcess update: > > > > Name: OSProcess-Base-dtl.56 > > Time: 17 January 2017, 8:47:36.321587 am > > > > OSProcess 4.6.7 > > > > Add nil checks in #shutDown: to prevent failures when exiting existing > > image with a VM that does not include OSPP (e.g. SqueakJS). > > > > For AIO event hander, if the AIO plugin is not present, write an error > > to console rather than interrupting the image with a notifer. Reduces the > > annoyance level if VM provider provides OSPP but neglects to include the > > AIO plugin. > > > > Dave > > > > > > >

Jan. 23, 2017

Re: [Pharo-dev] [Pharo6] Issue tracker: Issues tagged Pharo6

by Peter Uhnak

When is the release planned? Peter On Mon, Jan 23, 2017 at 11:58:19AM +0100, Marcus Denker wrote: > Hi, > > To be able to release, we have to check which issues are real show-stoppers. > > As a first step, we will, this Friday, remove the Pharo6 Milestone tag from *all* > issues that are priority âwould be niceâ or lower. > > https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i… <https://pharo.fogbugz.com/f/filters/?fGlobal=true&ixFixFor=22&ixPerson=46&i…> > > These are 281 issues right now. > > It would be nice if everyone would look at the issues that they have been involved in an adjust priority of needed. > > Marcus

Jan. 23, 2017