November 2017 - Pharo-users

Re: [Pharo-users] Removing instance variables doesn't recompile the methods

by Ben Coman

Thanks for reporting Abdelghani. Now it would be doubly useful if you could isolate which build introduced the problem. PharoLauncher can be used to help bisect working/non-working images. cheers -ben On 27 November 2017 at 04:08, abdelghani ALIDRA via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: abdelghani ALIDRA <alidrandco(a)yahoo.fr> > To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Sun, 26 Nov 2017 20:08:29 +0000 (UTC) > Subject: Removing instance variables doesn't recompile the methods > > Hi, > > In a fresh pharo 6 image, I add a class with an instance variable x and > implement accessors. > Then I write a test method for the accessors of x > MyClassTest>>testReadWriteX > self assert (MyClass new x: 0) x equals: 0 > > I run the test and obviously it is green > > BUT > > I remove the instance variable x. Obviously, the accessors are broken and > the test should be red when I execute it again but it is not!!! > > I can even change the class again (to recompile it I thought) or even load > the code in a new image and the tests are still green. > I can also invoque the broken methods in a playground or in an inspector : > MyClass new x: 0; increment; x then printIt. and astonishingly 1 is printed. > The only way to detect the error is to recompile the method but this does > not happen (maybe it should) when instance variables are modified or > removed in the class (even when you use the refactoring tool!) > > I think this is annoying because one can no more really trust his tests. > > Cheers > Abdelghani > > > >

Nov. 27, 2017

Re: [Pharo-users] How to write a little REPL

by Holger Freyther

> On 27. Nov 2017, at 05:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi Hey! > I'm working on a mini scheme implementation and I would like to add a REPL and > I wonder how I can super easily get a read line. The easiest might just be to use "rlwrap your-interpreter"? But I think you want to allow multi-line input. So either link libreadline (GPL) or libedit? holger

Nov. 27, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Stephane Ducasse

Hi Alistair If you want help I can add a baseline that automtically load DataFrame. Because users should not load by themselves external project. Stef On Sat, Nov 25, 2017 at 3:57 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Alistair Grant wrote >> https://github.com/PolyMathOrg/DataFrame > > Cool, thanks! I didn't know about this project. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Nov. 26, 2017

How to write a little REPL

by Stephane Ducasse

Hi I'm working on a mini scheme implementation and I would like to add a REPL and I wonder how I can super easily get a read line. Stef

Nov. 26, 2017

Re: [Pharo-users] I love the launcher!!!!

by phil＠highoctane.be

So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of the launcher... pharo6-64-ui PharoLauncher.image This interpreter (vers. 68021) cannot read image file (vers. 6521). Press CR to quit... How is one using the launcher for 64 bit stuff? Phil On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > If you don't try you will not understand what you miss. > > On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > > Stephane Ducasse wrote: > >> > >> Then do not try :) like that you will never get a chance to know :) > > > > > > Could you please explain? I understood your sentence has high dose of > homour > > which I cannot decipher since I lack certain abilities for that. > > > > Thanks, Herby > > > >> Stef > >> > >> > >> On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: > >>> > >>> Stephane Ducasse wrote: > >>>> > >>>> Why don't you try? It does not bite. > >>>> > >>>> For me it works in all scenario. I have projects that i manage over > >>>> several weeks and others I drop day to day. > >>>> And I have also startup script per versions. > >>> > >>> > >>> Maybe I will. The main problem was I didn't what it's good about at > all - > >>> load image for a version, runs it - what's the "wow it's great" about? > >>> Missed part was it loads correct vm; plus makes sense when you have > >>> hundreds > >>> (I don't). Now it must be combined with the startup script magic to > work > >>> with long-time projects, but those are also new to me - did not know of > >>> them > >>> until your booklet, not using them at all yet. > >>> > >>> Herby > >>> > >>> > >>>> Stef > >>>> > >>>> On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby(a)mailbox.sk> > wrote: > >>>>> > >>>>> Thank you all, now I understand it better. Good for lots of > "branches". > >>>>> > >>>>> However, I wonder how does it work with the rule I read somewhere: > >>>>> "start > >>>>> each day [of work on a project] with a new image", which means I > should > >>>>> not > >>>>> reuse clean new image (as it needs populating from VCSes etc.) nor > >>>>> reuse > >>>>> existing image (I should start with the new one). Or does it combine > >>>>> with > >>>>> some startup-magic described in one of the recent Steph's booklets, > the > >>>>> "one > >>>>> start per [new] image" case (but again, one should discriminate > >>>>> projects > >>>>> from each other)? > >>>>> > >>>>> Thanks, Herby > >>>>> > >>>>> Peter UhnÃ¡k wrote: > >>>>>> > >>>>>> Hi Herby, > >>>>>> > >>>>>> normally people use different images for their different projects, > >>>>>> different versions, trying things, etc. Which means we end up with > >>>>>> many > >>>>>> locations on disk, and it can be hard to track. > >>>>>> So PharoLauncher is a nice tool where you can download fresh image > >>>>>> just > >>>>>> by clicking, and you see the list of your local images and can > launch > >>>>>> them, etc. > >>>>>> > >>>>>> Peter > >>>>>> > >>>>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby(a)mailbox.sk > >>>>>> <mailto:herby@mailbox.sk>> wrote: > >>>>>> > >>>>>> Stephane Ducasse wrote: > >>>>>> > >>>>>> Hi > >>>>>> > >>>>>> I love the PharoLauncher. > >>>>>> > >>>>>> > >>>>>> Pardon my question, I have downloaded it and looked at it, > but I > >>>>>> don't get it. What does it do / what are the use cases (honest > >>>>>> question)? > >>>>>> > >>>>>> Thanks, Herby > >>>>>> > >>>>>> > >>>>>> It helps me to manage my parallel development and > projects. > >>>>>> > >>>>>> We should put a link on the Pharo web site because > >>>>>> > >>>>>> http://files.pharo.org/platform/launcher/ > >>>>>> <http://files.pharo.org/platform/launcher/> > >>>>>> > >>>>>> is arcane. > >>>>>> > >>>>>> Stef > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>> > >> > > > > > > >

Nov. 26, 2017

Re: [Pharo-users] Removing instance variables doesn't recompile the methods

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/20765/removing-an-instance-variable-does-… On Sun, Nov 26, 2017 at 9:50 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi abdel > > I created a class with x and two accessors and I created the same test > than you. They were green. > Then I removed the instance variable x > and I run the tests and they were greeeeeeeeennnnnnnnnnn (agrhhhhhhhh) > > I checked the accessors and the methods where showing that the > instance variable is missing. > > So to me this is indeed a bug. I have no idea why the test should run. > > Stef > > On Sun, Nov 26, 2017 at 9:08 PM, abdelghani ALIDRA via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> >> >> ---------- Forwarded message ---------- >> From: abdelghani ALIDRA <alidrandco(a)yahoo.fr> >> To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> >> Cc: >> Bcc: >> Date: Sun, 26 Nov 2017 20:08:29 +0000 (UTC) >> Subject: Removing instance variables doesn't recompile the methods >> >> Hi, >> >> In a fresh pharo 6 image, I add a class with an instance variable x and implement accessors. >> Then I write a test method for the accessors of x >> MyClassTest>>testReadWriteX >> self assert (MyClass new x: 0) x equals: 0 >> >> I run the test and obviously it is green >> >> BUT >> >> I remove the instance variable x. Obviously, the accessors are broken and the test should be red when I execute it again but it is not!!! >> >> I can even change the class again (to recompile it I thought) or even load the code in a new image and the tests are still green. >> I can also invoque the broken methods in a playground or in an inspector : MyClass new x: 0; increment; x then printIt. and astonishingly 1 is printed. >> The only way to detect the error is to recompile the method but this does not happen (maybe it should) when instance variables are modified or removed in the class (even when you use the refactoring tool!) >> >> I think this is annoying because one can no more really trust his tests. >> >> Cheers >> Abdelghani >> >> >>

Nov. 26, 2017

Re: [Pharo-users] Removing instance variables doesn't recompile the methods

by Stephane Ducasse

Hi abdel I created a class with x and two accessors and I created the same test than you. They were green. Then I removed the instance variable x and I run the tests and they were greeeeeeeeennnnnnnnnnn (agrhhhhhhhh) I checked the accessors and the methods where showing that the instance variable is missing. So to me this is indeed a bug. I have no idea why the test should run. Stef On Sun, Nov 26, 2017 at 9:08 PM, abdelghani ALIDRA via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: abdelghani ALIDRA <alidrandco(a)yahoo.fr> > To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Sun, 26 Nov 2017 20:08:29 +0000 (UTC) > Subject: Removing instance variables doesn't recompile the methods > > Hi, > > In a fresh pharo 6 image, I add a class with an instance variable x and implement accessors. > Then I write a test method for the accessors of x > MyClassTest>>testReadWriteX > self assert (MyClass new x: 0) x equals: 0 > > I run the test and obviously it is green > > BUT > > I remove the instance variable x. Obviously, the accessors are broken and the test should be red when I execute it again but it is not!!! > > I can even change the class again (to recompile it I thought) or even load the code in a new image and the tests are still green. > I can also invoque the broken methods in a playground or in an inspector : MyClass new x: 0; increment; x then printIt. and astonishingly 1 is printed. > The only way to detect the error is to recompile the method but this does not happen (maybe it should) when instance variables are modified or removed in the class (even when you use the refactoring tool!) > > I think this is annoying because one can no more really trust his tests. > > Cheers > Abdelghani > > >

Nov. 26, 2017

Re: [Pharo-users] I love the launcher!!!!

by Stephane Ducasse

If you don't try you will not understand what you miss. On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Stephane Ducasse wrote: >> >> Then do not try :) like that you will never get a chance to know :) > > > Could you please explain? I understood your sentence has high dose of homour > which I cannot decipher since I lack certain abilities for that. > > Thanks, Herby > >> Stef >> >> >> On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>> >>> Stephane Ducasse wrote: >>>> >>>> Why don't you try? It does not bite. >>>> >>>> For me it works in all scenario. I have projects that i manage over >>>> several weeks and others I drop day to day. >>>> And I have also startup script per versions. >>> >>> >>> Maybe I will. The main problem was I didn't what it's good about at all - >>> load image for a version, runs it - what's the "wow it's great" about? >>> Missed part was it loads correct vm; plus makes sense when you have >>> hundreds >>> (I don't). Now it must be combined with the startup script magic to work >>> with long-time projects, but those are also new to me - did not know of >>> them >>> until your booklet, not using them at all yet. >>> >>> Herby >>> >>> >>>> Stef >>>> >>>> On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby(a)mailbox.sk> wrote: >>>>> >>>>> Thank you all, now I understand it better. Good for lots of "branches". >>>>> >>>>> However, I wonder how does it work with the rule I read somewhere: >>>>> "start >>>>> each day [of work on a project] with a new image", which means I should >>>>> not >>>>> reuse clean new image (as it needs populating from VCSes etc.) nor >>>>> reuse >>>>> existing image (I should start with the new one). Or does it combine >>>>> with >>>>> some startup-magic described in one of the recent Steph's booklets, the >>>>> "one >>>>> start per [new] image" case (but again, one should discriminate >>>>> projects >>>>> from each other)? >>>>> >>>>> Thanks, Herby >>>>> >>>>> Peter UhnÃ¡k wrote: >>>>>> >>>>>> Hi Herby, >>>>>> >>>>>> normally people use different images for their different projects, >>>>>> different versions, trying things, etc. Which means we end up with >>>>>> many >>>>>> locations on disk, and it can be hard to track. >>>>>> So PharoLauncher is a nice tool where you can download fresh image >>>>>> just >>>>>> by clicking, and you see the list of your local images and can launch >>>>>> them, etc. >>>>>> >>>>>> Peter >>>>>> >>>>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby(a)mailbox.sk >>>>>> <mailto:herby@mailbox.sk>> wrote: >>>>>> >>>>>> Stephane Ducasse wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> I love the PharoLauncher. >>>>>> >>>>>> >>>>>> Pardon my question, I have downloaded it and looked at it, but I >>>>>> don't get it. What does it do / what are the use cases (honest >>>>>> question)? >>>>>> >>>>>> Thanks, Herby >>>>>> >>>>>> >>>>>> It helps me to manage my parallel development and projects. >>>>>> >>>>>> We should put a link on the Pharo web site because >>>>>> >>>>>> http://files.pharo.org/platform/launcher/ >>>>>> <http://files.pharo.org/platform/launcher/> >>>>>> >>>>>> is arcane. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> >>> >> > >

Nov. 26, 2017

Removing instance variables doesn't recompile the methods

by abdelghani ALIDRA

Hi, In a fresh pharo 6 image, I add a class with an instance variable x and implement accessors. Then I write a test method for the accessors of x MyClassTest>>testReadWriteX Â Â Â self assert (MyClass new x: 0) x equals: 0 I run the test and obviously it is green BUT I remove the instance variable x. Obviously, the accessors are broken and the test should be red when I execute it again but it is not!!! I can even change the class again (to recompile it I thought) or even load the code in a new image and the tests are still green. I can also invoque the broken methods in a playground or in an inspector : MyClass new x: 0; increment; x then printIt. and astonishingly 1 is printed. The only way to detect the error is to recompile the method but this does not happen (maybe it should) when instance variables are modified or removed in the class (even when you use the refactoring tool!) I think this is annoying because one can no more really trust his tests. Cheers Abdelghani

Nov. 26, 2017

Re: [Pharo-users] Pharo-users Digest, Vol 55, Issue 206

by Herby VojÄÃk

Ben Coman wrote: > > > On 26 November 2017 at 21:28, Herby VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > Ben Coman wrote: > > > > On 25 November 2017 at 15:18, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² > <vikenti.potapov(a)gmail.com <mailto:vikenti.potapov@gmail.com> > <mailto:vikenti.potapov@gmail.com > <mailto:vikenti.potapov@gmail.com>>> wrote: > > > I downloaded the latest PharoLauncher image, use VM for > Pharo 6.1. > 1) On load i got an error with UTF8 encoding. > 2) Every time i tried to create image (for example, Pharo 7 > image) i > get an error "Can't find the requested origin". > > Reported. > > Best regards, Vikenti Potapov > > > The overall difficulty here in getting this addressed is > difficulty in > reproducing your environment. > For example, I think it would be awkward for me to operate with OS > locale set to Russian. > You'll see little action on it until there is an Issue logged at > pharo.fogbugz.com <http://pharo.fogbugz.com> > <http://pharo.fogbugz.com/> with a simple set of steps > to reproduced for standard environments (i.e. using English locales) > > Reviewing your other posts, I'd suggest initially creating a > script to > wrap Pharo startup that cleans all the environment variables to > ascii > > > -1. > > It should all work in other locales. Maybe you should set some if > not all of the jenkins jobs under different locales (at least > russian and japanese) to catch those things fast. > > Your (I hate to use the word) privilege to be fine with ASCII only > actually masks lot of bugs from you. > > > I think you misunderstand me. This suggestion was only to help isolate > the problem during troubleshooting. > The best way to troubleshoot something is to a.) start with something > working and then b.) be able to reliability break it. > Vikenti doesn't have (a.) so I was giving him a hack to get that, to be > able to proceed to (b.) > > But your suggestion to the running some CI jobs under different locals > and timezones could be useful. Ok, sorry. Herby > cheers -ben > > > > Herby > > P.S.: Other masking thing is the timezone which is UTC in case of > UK, France and lot of the rest of Western Europe. That should also > be set to. say, Sydney and Honolulu to get big GMT+ and GMT- shifts. > > > characters, temporarily creating required directories so at lest > you can > get it started. Then extend that script to reintroduce the > error, like > a single non-ascii character in a single environment variable that > causes an error. That extended part then provides a path for > others to > reproduce your problem, which you would attach to the Issue. > Then as > you investigate a solution yourself, ask questions about it on > pharo-dev > to keep the Issue active and over time you'll likely get some action > from others on it. > > cheers -ben > > > > > >

Nov. 26, 2017