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

Re: [Pharo-dev] 08/05/17 - Tabular Data Structures for Data Analysis - Oleksandr Zaytsev

by Denis Kudriashov

2017-05-09 18:44 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > I get 21 errors, since they have code like this... > self assert: (Smalltalk globals classNamed: originalName) isNil. > we should replace such places with Smalltalk globals includeClassNamed: originalName

May 9, 2017

Re: [Pharo-dev] 08/05/17 - Tabular Data Structures for Data Analysis - Oleksandr Zaytsev

by Eliot Miranda

Hi Ben, On Tue, May 9, 2017 at 9:44 AM, Ben Coman <btc(a)openinworld.com> wrote: > [redirected from pharo-gsoc to pharo-dev] > > On Tue, May 9, 2017 at 7:36 AM, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com> > wrote: > > A. Improved my fix of this case: https://pharo.fogbugz.com/f/cases/19396, > as > > suggested by Ben Coman, and created a slice for it (I think it works > like PR > > in Pharo - correct me if I'm wrong). > > Thanks Olek. The slice is good, and the additional test is good. > > Now after loading the slice and running all system tests from World > > TestRunner > I get 21 errors, since they have code like this... > self assert: (Smalltalk globals classNamed: originalName) isNil. > which needs to be updated and checked that there is no clash in usage. > > Anyone know of a method like... > self assert: (Smalltalk globals classNamed: originalName) raised: > ClassNotFound. > Hmmm, classNamed: has always answered nil for nonexistent classes. Did this get changed? Not sure that's right. Why not add checkedClassNamed: or some such? > which seems more useful than each time doing... > | correctErrorRaised | > correctErrorRaised := false. > [ Smalltalk globals classNamed: #notExistedClass ] > on: ClassNotFound do: [correctErrorRaised := true]. > self assert: correctErrorRaised. > > > btw, one of the failures is ClassTest>>testMethodsReferencingClass > but I'm a little confused by... > self assert: (ClassTest methodsReferencingClass: (Smalltalk > classNamed: #BehaviorTests)) isEmpty > > since there is no "BehaviorTests" in the Image, which effectively is... > self assert: (ClassTest methodsReferencingClass: nil) isEmpty > So is this succeeding by accident? @Pavel, @Vicent can you advise? > i guess it should be BehaviorTest not BehaviorTests, which goes to > show the value > of #classNamed: raising ClassNotFound instead of returning nil. > > cheers -ben > > -- _,,,^..^,,,_ best, Eliot

May 9, 2017

Re: [Pharo-dev] Adding class side inst.var to a class using Trait results in nil message sent

by Stephane Ducasse

Aliaksei thanks for the report. Now if you do not say in the title that this looks like an Epicea problem then Martin may not see it. Can you open a bug entry? Stef On Mon, May 8, 2017 at 10:57 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi, > > Screenshot tells everything :) > I was trying to add "asdasd" inst var > > [image: Inline images 1] > > Cheers, > Alex >

May 9, 2017

Re: [Pharo-dev] Introduction (GSoC)

by Stephane Ducasse

Welcome Rajula :) And yes I'm eager to see clap replace the old commandline handler Stef On Tue, May 9, 2017 at 1:04 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Welcome, Rajula. > > Please keep us posted with the progress. > > Cheers, > Doru > > > > > On May 9, 2017, at 12:45 PM, Rajula Vineet <Vineet.Reddy(a)iiitb.org> > wrote: > > > > Hi all, > > > > I am Rajula. Firstly I would like to thank the community especially > Guille > > and StÃ©phane Ducasse for their support and guidance. I am glad that I > have > > been given the opportunity to work on the GSoC project 'Enhancing Pharo > > Command Line Interface' this summer. > > > > The main goals of the project are > > > > 1) implementing clap for pharo > > 2) fixing logging and general file management > > 3) fixing current working directory > > > > The mentors for my project are Guille Polito, Philippe Back, and emBee. > I am > > looking forward to an amazing summer ahead. If you have any suggestions > for > > the project, I would be happy to consider them. > > > > Thanks again for the opportunity. > > > > Rajula. > > > > > > > > -- > > View this message in context: http://forum.world.st/ > Introduction-GSoC-tp4946020.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > -- > www.tudorgirba.com > www.feenk.com > > "We cannot reach the flow of things unless we let go." > > > > > >

May 9, 2017

Re: [Pharo-dev] 08/05/17 - Tabular Data Structures for Data Analysis - Oleksandr Zaytsev

by Ben Coman

[redirected from pharo-gsoc to pharo-dev] On Tue, May 9, 2017 at 7:36 AM, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com> wrote: > A. Improved my fix of this case: https://pharo.fogbugz.com/f/cases/19396, as > suggested by Ben Coman, and created a slice for it (I think it works like PR > in Pharo - correct me if I'm wrong). Thanks Olek. The slice is good, and the additional test is good. Now after loading the slice and running all system tests from World > TestRunner I get 21 errors, since they have code like this... self assert: (Smalltalk globals classNamed: originalName) isNil. which needs to be updated and checked that there is no clash in usage. Anyone know of a method like... self assert: (Smalltalk globals classNamed: originalName) raised: ClassNotFound. which seems more useful than each time doing... | correctErrorRaised | correctErrorRaised := false. [ Smalltalk globals classNamed: #notExistedClass ] on: ClassNotFound do: [correctErrorRaised := true]. self assert: correctErrorRaised. btw, one of the failures is ClassTest>>testMethodsReferencingClass but I'm a little confused by... self assert: (ClassTest methodsReferencingClass: (Smalltalk classNamed: #BehaviorTests)) isEmpty since there is no "BehaviorTests" in the Image, which effectively is... self assert: (ClassTest methodsReferencingClass: nil) isEmpty So is this succeeding by accident? @Pavel, @Vicent can you advise? i guess it should be BehaviorTest not BehaviorTests, which goes to show the value of #classNamed: raising ClassNotFound instead of returning nil. cheers -ben

May 9, 2017

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

by Esteban Lorenzano

no reason to complain, I was saying that we are expectantly waiting :D Esteban > On 9 May 2017, at 18:22, Norbert Hartl <norbert(a)hartl.name> wrote: > > Me, too. But all the work is done by Holger because I don't find time. So no reason to complain for me ð¬ > > Norbert > >> Am 09.05.2017 um 17:13 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >> yes, we are waiting for that :) >> >>> On 9 May 2017, at 17:10, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >>> >>> >>>> Am 09.05.2017 um 16:46 schrieb Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>>: >>>> >>>> >>>>> On 9 May 2017, at 16:10, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>>> >>>>> http://pharo.org/STAGE.gnu-linux-installation <http://pharo.org/STAGE.gnu-linux-installation> >>>>> >>>>> I donât think they will work. >>>>> We need to update or remove. >>>>> >>>>> Esteban >>>> >>>> It is impossible to support all the Linux distros out there, they are a PIA if you ask may. There are regularly people asking support for weird distros that are maybe used by just a couple of people (if that many). I think we should have a short list of supported distros, all the others should be contributed. >>> >>> The basic list of supported targets will be close to this list >>> >>> https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets <https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets> >>> >>> Meaning all "could" be supported if necessary and if there aren't technical issues why it cannot be supported. >>> >>> People with not so common distros need proper build instructions to do it themselves. >>> >>> Norbert >>> >> >

May 9, 2017

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

by Norbert Hartl

Me, too. But all the work is done by Holger because I don't find time. So no reason to complain for me ð¬ Norbert > Am 09.05.2017 um 17:13 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > yes, we are waiting for that :) > >> On 9 May 2017, at 17:10, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: >> >> >>> Am 09.05.2017 um 16:46 schrieb Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>>: >>> >>> >>>> On 9 May 2017, at 16:10, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>>> >>>> http://pharo.org/STAGE.gnu-linux-installation <http://pharo.org/STAGE.gnu-linux-installation> >>>> >>>> I donât think they will work. >>>> We need to update or remove. >>>> >>>> Esteban >>> >>> It is impossible to support all the Linux distros out there, they are a PIA if you ask may. There are regularly people asking support for weird distros that are maybe used by just a couple of people (if that many). I think we should have a short list of supported distros, all the others should be contributed. >> >> The basic list of supported targets will be close to this list >> >> https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets <https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets> >> >> Meaning all "could" be supported if necessary and if there aren't technical issues why it cannot be supported. >> >> People with not so common distros need proper build instructions to do it themselves. >> >> Norbert >> >

May 9, 2017

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

by Esteban Lorenzano

yes, we are waiting for that :) > On 9 May 2017, at 17:10, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 09.05.2017 um 16:46 schrieb Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>>: >> >> >>> On 9 May 2017, at 16:10, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >>> >>> http://pharo.org/STAGE.gnu-linux-installation <http://pharo.org/STAGE.gnu-linux-installation> >>> >>> I donât think they will work. >>> We need to update or remove. >>> >>> Esteban >> >> It is impossible to support all the Linux distros out there, they are a PIA if you ask may. There are regularly people asking support for weird distros that are maybe used by just a couple of people (if that many). I think we should have a short list of supported distros, all the others should be contributed. > > The basic list of supported targets will be close to this list > > https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets <https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets> > > Meaning all "could" be supported if necessary and if there aren't technical issues why it cannot be supported. > > People with not so common distros need proper build instructions to do it themselves. > > Norbert >

May 9, 2017

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

by Norbert Hartl

> Am 09.05.2017 um 16:46 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > >> On 9 May 2017, at 16:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> http://pharo.org/STAGE.gnu-linux-installation >> >> I donât think they will work. >> We need to update or remove. >> >> Esteban > > It is impossible to support all the Linux distros out there, they are a PIA if you ask may. There are regularly people asking support for weird distros that are maybe used by just a couple of people (if that many). I think we should have a short list of supported distros, all the others should be contributed. The basic list of supported targets will be close to this list https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets <https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets> Meaning all "could" be supported if necessary and if there aren't technical issues why it cannot be supported. People with not so common distros need proper build instructions to do it themselves. Norbert

May 9, 2017

Re: [Pharo-dev] preparing to release: what do we do with this linux distros?

by Sven Van Caekenberghe

> On 9 May 2017, at 16:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > http://pharo.org/STAGE.gnu-linux-installation > > I donât think they will work. > We need to update or remove. > > Esteban It is impossible to support all the Linux distros out there, they are a PIA if you ask may. There are regularly people asking support for weird distros that are maybe used by just a couple of people (if that many). I think we should have a short list of supported distros, all the others should be contributed.

May 9, 2017