November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] class variable slots?

by Eliot Miranda

Hi Tudor, On Wed, Nov 26, 2014 at 6:02 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > As far as I see, the class variables are not slots. Is that correct? > That's right. They're associations in class pools, and are visible in the instance-side and class-side methods of the class and all its subclasses. See Class>>bindingOf: and Class's inst var classPool. Shared pools are similar. A shared pool stores its variables in its class pool, but other classes can have its class vars in scope by including the shared pool in its pool dictionaries. > If not, how do I get the slots? > Well, just for clarity (at least I hope it'll bring clarity). One can access the variables via MyClass classPool associations Note that these are entirely different from class instance variables, which are inst var slots in the class object. These hold things like the class's superclass, its method dictionary, etc. But one can add inst vars to one's own class. There are many examples of this. Since these slots are per-class every class gets its own copy of the slot, and because these are inst vars, they are only in scope in class-side methods of the defining class and subclasses. HTH > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- best, Eliot

Nov. 26, 2014

IdentitySet>>collect:

by Eliot Miranda

Hi All, IdentitySet>>collect: answers a Set, not an IdentitySet. Anyone else agree this is a serious bug? Anyone else disagree? WTF?? (IdentitySet withAll: #(1 2 3 1.0 2.0 3.0)) collect: [:e| e] a Set(1.0 2 3) -- best, Eliot

Nov. 26, 2014

Re: [Pharo-dev] Stream instead of string concatenation

by Ben Coman

Yuriy Tymchuk wrote: > Hi everyone! > > There is a Lint rule that suggests to use stream instead of strings concatenation. What is the most common way, to create a string this way, because the only thing I can come up with is: > > String streamContents: [ :stream | > stream > nextPutAll: 'Hello'; > nextPut: $ ; > nextPutAll: 'Worldâ] > > But Iâm not sure if it is the preferred solution. > > Cheers > Uko > This is typical advise, but previous discussion found it to be not necessarily true. https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg08162.html Perhaps the rule should be ammended/deleted. cheers -ben

Nov. 26, 2014

Re: [Pharo-dev] Stream instead of string concatenation

by Max Leske

> On 26.11.2014, at 17:18, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone! > > There is a Lint rule that suggests to use stream instead of strings concatenation. What is the most common way, to create a string this way, because the only thing I can come up with is: > > String streamContents: [ :stream | > stream > nextPutAll: 'Hello'; > nextPut: $ ; > nextPutAll: 'Worldâ] > > But Iâm not sure if it is the preferred solution. Yes, thatâs what I do. With one addition: The default size for such a stream is 100, so if I know that my collection is going to be significantly larger / smaller I initialize the collection directly: String new: 400 streamContents [: â¦. And for everyone who hasnât yet discovered it: #streamContents is implemented on SequenceableCollection! That means you can do the same thing with arrays, orderedCollections etc. Streaming is awesome :) > > Cheers > Uko

Nov. 26, 2014

Re: [Pharo-dev] Stream instead of string concatenation

by Luc Fabresse

Hi Uko, 2014-11-26 17:18 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi everyone! > > There is a Lint rule that suggests to use stream instead of strings > concatenation. What is the most common way, to create a string this way, > because the only thing I can come up with is: > > String streamContents: [ :stream | > stream > nextPutAll: 'Hello'; > nextPut: $ ; > nextPutAll: 'Worldâ] > > But Iâm not sure if it is the preferred solution. > Yes, I use this too. and I use << instead of #nextPutAll: Cheers, Luc > > Cheers > Uko >

Nov. 26, 2014

Stream instead of string concatenation

by Yuriy Tymchuk

Hi everyone! There is a Lint rule that suggests to use stream instead of strings concatenation. What is the most common way, to create a string this way, because the only thing I can come up with is: String streamContents: [ :stream | stream nextPutAll: 'Hello'; nextPut: $ ; nextPutAll: 'Worldâ] But Iâm not sure if it is the preferred solution. Cheers Uko

Nov. 26, 2014

Pharo-4.0-Update-Step-3-Minimal versus MCWorkingCopyBrowser

by Ben Coman

I am checking why the .10 slice for Issue-14261-Delay-refactoring-part-1 is breaking build of the Jenkins > Pharo-4.0-Update-Step-3-Minimal. As an aside, I discovered opening (and closing) Monticello in the image prior to running shrink.st makes it fragile. With the scripts for build 40384 from... https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-3-Minimal/243/ 1. I opened the 40384.image with pharo-ui 2. Opened Monticello and browsed to the .10 slice of issue 14261 but did not load it 3. Saved the image 4. Ran my cobbled ./shrink.sh shown here... #!/bin/bash -x IMAGE=Pharo-minimal # wget -O - http://get.pharo.org/vm | bash ./pharo *.image save $IMAGE --delete-old ./pharo $IMAGE.image unloadNB.st ./pharo $IMAGE.image cleanAfterNB.st ./pharo $IMAGE.image prepareShrink.st ./pharo $IMAGE.image shrink.st which fails with... 11 IndentingListItemMorph(Object)>>doesNotUnderstand: #theme 12 IndentingListItemMorph(StringMorph)>>defaultColor 13 IndentingListItemMorph(Morph)>>initialize ... 23 MCWorkingCopyBrowser(Object)>>changed: shrink.st is more robust with the following... MCWorkingCopyBrowser allInstances do: [ :mcwcb | SystemAnnouncer uniqueInstance unsubscribe: mcwcb ]. added to shrink.st. I put it after existing line... SystemAnnouncer uniqueInstance unsubscribe: NOCCompletionTable. HTH, cheers -ben

Nov. 26, 2014

Re: [Pharo-dev] Athens Repository (NativeBoost)

by Nicolai Hess

2014-11-26 14:54 GMT+01:00 Igor Stasenko <siguctua(a)gmail.com>: > > > On 26 November 2014 at 08:33, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> >> On 25 Nov 2014, at 23:39, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >> >> >> 2014-11-24 23:34 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> both are integrated into the image. >>> while NB has been maintained directly, athens should still be loadable >>> (if not the caseâ¦ we have a problem for the future :P). >>> >> >> what does that mean for athens, yes unload and loadable from the image or >> loadable from the sthub repository? >> >> >> > The process is simple: > - Athens has own repository where its sources are maintained and updated > etc.. > - an updates then can be loaded into Pharo image(s), so it can come with > Pharo distribution by default. > > It is important to keep this project in separate repository, that helps > with managing it and producing predictable results. > Ah, that is what I wanted to know. > The fact that Athens are part of Pharo distribution don't means, that its > repository should be abandoned and all updates should come directly to > Pharo. That would be a huge mistake. > That's how I've done it recently. I'll merge the changes from pharo -> athens repository. > Doing everything in a monolithic image is a planning mess, and works fine > only for bug fixing or small refactorings. > > Anything which requires sizable planning and designing, should have own > line of development and maintenance, > like that there's a clear separation of the responsibility for maintaining > the project in healthy state and less bottlenecks. > > > no ideaâ¦ I guess is the same case, but I have no control over that area. >> Igor will know better :) >> >> Esteban >> >> >> > > -- > Best regards, > Igor Stasenko. >

Nov. 26, 2014

class variable slots?

by Tudor Girba

Hi, As far as I see, the class variables are not slots. Is that correct? If not, how do I get the slots? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Nov. 26, 2014

Re: [Pharo-dev] Athens Repository (NativeBoost)

by Igor Stasenko

On 26 November 2014 at 08:33, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 25 Nov 2014, at 23:39, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2014-11-24 23:34 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> both are integrated into the image. >> while NB has been maintained directly, athens should still be loadable >> (if not the caseâ¦ we have a problem for the future :P). >> > > what does that mean for athens, yes unload and loadable from the image or > loadable from the sthub repository? > > > The process is simple: - Athens has own repository where its sources are maintained and updated etc.. - an updates then can be loaded into Pharo image(s), so it can come with Pharo distribution by default. It is important to keep this project in separate repository, that helps with managing it and producing predictable results.The fact that Athens are part of Pharo distribution don't means, that its repository should be abandoned and all updates should come directly to Pharo. That would be a huge mistake. Doing everything in a monolithic image is a planning mess, and works fine only for bug fixing or small refactorings. Anything which requires sizable planning and designing, should have own line of development and maintenance, like that there's a clear separation of the responsibility for maintaining the project in healthy state and less bottlenecks. no ideaâ¦ I guess is the same case, but I have no control over that area. > Igor will know better :) > > Esteban > > > -- Best regards, Igor Stasenko.

Nov. 26, 2014