April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Sorry - Please Stay!!!

by Stephane Ducasse

I think that I will simply stop to read this mailing-list too. Like that I will get focused and do not get hurt systematically by all the wish list and santa klaus dreams around. I'm a bit feedup about the stream of "YouShouldDoIt" and also the ton of certain mails. Stef On Sun, Apr 22, 2018 at 6:46 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > +1 > > On Sun, Apr 22, 2018 at 2:29 PM, <sean(a)clipperadams.com> wrote: >>> Well, I guess I don't belong here anymoreâ¦ >> >> Please don't let one personality define our community. I'm sure there are a lot of people, like me, who appreciate your perspective and efforts. Steph has said the same thing to me multiple times about talking vs. action and I've worked on hundreds of issues. It can be frustrating, but I certainly believe it's worth it because while not perfect, Pharo is the closest to my Dynabook dream with enough of a community around it to have good up-to-date libraries around it, etc. GT, Roassal, Grafoscopio, and the new AI stuff are getting really exciting. Let's focus on inventing the future! >> >> _____________________________________ >> Sent from http://forum.world.st >> >>

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Stephane Ducasse

Indeed TestCase is a really a special class and it can be really looking strange at first. On Sun, Apr 22, 2018 at 2:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Gregg Williams wrote >> HiâIâm a beginner in Pharo and am working my way through Pharo by Example >> 5.0 (PbE) and Learning OOP and TDD with Pharo (LOTWP). > > Welcome! That's a great way to start :) > > > Gregg Williams wrote >> 1) These two methods are defined on the instance side (the Class button is >> *not* selected). If so, what is the receiver when they are used? > > I think the other two replies covered this and your other questions > technically, but I just want to mention that the TestCase class can be a bit > confusing. It represents a convenient way to deal with tests in a class > browser, at the expense of being the most understandable OOP design. Suffice > it to say that whenever a test is run, SUnit, the testing system, will do > the magic to create an instance of your TestCase subclass. This is what > happens when you click the test bubble in the browser, and this instance is > what `self` refers to in tests. HTH > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

April 22, 2018

Re: [Pharo-users] Sorry - Please Stay!!!

by Stephane Ducasse

+1 On Sun, Apr 22, 2018 at 2:29 PM, <sean(a)clipperadams.com> wrote: >> Well, I guess I don't belong here anymoreâ¦ > > Please don't let one personality define our community. I'm sure there are a lot of people, like me, who appreciate your perspective and efforts. Steph has said the same thing to me multiple times about talking vs. action and I've worked on hundreds of issues. It can be frustrating, but I certainly believe it's worth it because while not perfect, Pharo is the closest to my Dynabook dream with enough of a community around it to have good up-to-date libraries around it, etc. GT, Roassal, Grafoscopio, and the new AI stuff are getting really exciting. Let's focus on inventing the future! > > _____________________________________ > Sent from http://forum.world.st > >

April 22, 2018

Escaping from FileStream

by Hilaire

For example when rewritting this methods, to read afterward PNG image I have error: image format no recognized. getFile: aFilename "Â Â Â ^ FileStream readOnlyFileNamed: (self fullname: aFilename)" Â Â Â ^ (self fullname: aFilename) asFileReference binaryReadStream Le 22/04/2018 Ã 16:46, Hilaire a Ã©critÂ : > A migration guide will be more than welcome, because the API, and > likely the logic, is different. > > Thanks > > Hilaire > > > Le 21/04/2018 Ã 13:37, Sven Van Caekenberghe a Ã©critÂ : >> Yes, relatively recent, weeks I guess, maybe a month, at least since >> half March. >> >> FileSystem (part of the image for ages), File and new streams (most >> also long part of the image) are the replacements. >> >> BTW, I meant [Abstract]FileReference>>#fileIn which is a unary selector. -- Dr. Geo http://drgeo.eu

April 22, 2018

Re: [Pharo-users] Proper way to file in code

by Hilaire

A migration guide will be more than welcome, because the API, and likely the logic, is different. Thanks Hilaire Le 21/04/2018 Ã 13:37, Sven Van Caekenberghe a Ã©critÂ : > Yes, relatively recent, weeks I guess, maybe a month, at least since half March. > > FileSystem (part of the image for ages), File and new streams (most also long part of the image) are the replacements. > > BTW, I meant [Abstract]FileReference>>#fileIn which is a unary selector. -- Dr. Geo http://drgeo.eu

April 22, 2018

Re: [Pharo-users] What next for Pharo vm?

by Ben Coman

On 22 April 2018 at 22:03, henry <henry(a)callistohouse.club> wrote: > I was thinking the vm is able to run more than one bytecode set. Why > couldnât our vm support both Pharo and Java bytecodes? > > Some previous discussion here... http://forum.world.st/java-interpreter-compiler-hosted-with-Spur-td4739237.… cheers -ben

April 22, 2018

What next for Pharo vm?

by henry

I was thinking the vm is able to run more than one bytecode set. Why couldnât our vm support both Pharo and Java bytecodes? Sent from ProtonMail Mobile

April 22, 2018

Sorry - Please Stay!!!

by sean＠clipperadams.com

> Well, I guess I don't belong here anymoreâ¦ Please don't let one personality define our community. I'm sure there are a lot of people, like me, who appreciate your perspective and efforts. Steph has said the same thing to me multiple times about talking vs. action and I've worked on hundreds of issues. It can be frustrating, but I certainly believe it's worth it because while not perfect, Pharo is the closest to my Dynabook dream with enough of a community around it to have good up-to-date libraries around it, etc. GT, Roassal, Grafoscopio, and the new AI stuff are getting really exciting. Let's focus on inventing the future! _____________________________________ Sent from http://forum.world.st

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Sean P. DeNigris

Gregg Williams wrote > HiâIâm a beginner in Pharo and am working my way through Pharo by Example > 5.0 (PbE) and Learning OOP and TDD with Pharo (LOTWP). Welcome! That's a great way to start :) Gregg Williams wrote > 1) These two methods are defined on the instance side (the Class button is > *not* selected). If so, what is the receiver when they are used? I think the other two replies covered this and your other questions technically, but I just want to mention that the TestCase class can be a bit confusing. It represents a convenient way to deal with tests in a class browser, at the expense of being the most understandable OOP design. Suffice it to say that whenever a test is run, SUnit, the testing system, will do the magic to create an instance of your TestCase subclass. This is what happens when you click the test bubble in the browser, and this instance is what `self` refers to in tests. HTH ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 22, 2018

Re: [Pharo-users] question re. meaning of 'self' in a method used for testing

by Stephane Ducasse

tx guys for your help. cleaning the garden (was a junggle -well still). On Sun, Apr 22, 2018 at 12:18 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 22/04/2018 Ã 05:25, Gregg Williams a Ã©crit : >> >> 2) In testAllIsogramSet, why do you need âselfâ? After all âisogramsâ is a >> data structure, and its message is âdo:â > > > You defined isograms as a method of the class. Therefore only this method > returns the data structure you defined there. > It is not an instance variable declared in your GramCheckerTest class. In > that case you may want to initialize it in your initialize GramCheckerTest > class (or for a test case it is better to do it it in the setUp method as it > will be called before each test method call): > > initialize > super initialize. > isograms := #('pharo' 'pathfinder' 'xavier' 'lumberjacksâ) > > > Then your test method can access it directly (without self): > > > isograms do: [ :word | self assert: word isIsogramSet ] > > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

April 22, 2018