March 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

by Tim Mackinnon

And looking at this in the code - there are quite a few variations of #includesâ¦ that I donât think it makes sense to write the mirror of all of them. Not it is... > On 18 Mar 2019, at 16:48, Tim Mackinnon <tim(a)testit.works> wrote: > > Thanks guys - I always learn something new from these threads. > >> On 17 Mar 2019, at 06:56, Richard O'Keefe <raoknz(a)gmail.com <mailto:raoknz@gmail.com>> wrote: >> >> (1) As it happens, my Smalltalk library *does* have >> #excludes: and #identityExcludes: >> (2) The definitions are trivial. >> excludes: item >> ^(self includes: item) not >> identityExcludes: item >> ^(self identityIncludes: item) not >> >> If you want to execute aBlock when aString is not all zeros >> and ones, just do >> (aString allSatisfy: [:each | each = $0 or: [each = $1]]) >> ifFalse: [aBlock value]. >> or >> (aString anySatisfy: [:each | each ~= $0 and: [each ~= $1]]) >> ifTrue: [aBlock value]. >> or >> ('01' includesAll: aString) ifFalse: [aBlock value]. >> >> >> On Sat, 16 Mar 2019 at 11:33, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> Hi - in my quest to understand the edgier details of Pharo (and Smalltalk) - and driven by fresh thoughts of completing exercism exercises - I was surprised to find that there is no #excludes: operation on collection to mirror the #includes: operation? >> >> I was curious about this - its seems a strange omission? >> >> Of course I can inverse it with not, or do things a different way - but we have ifTrue: mirrored with ifFalse, empty/notEmpty so am I missing something? >> >> I wanted to write something like >> >> >> aString detect: [:c | ($0 to: $1) excludes: c] ifFound: aBlock. (Evaluate a block if the string isnât all 0 and 1âs) >> >> >> Of course I can write this as: >> >> (aString reject: [:c | c = $0 | c = $1)) ifNotEmpty: aBlock >> >> But as recent messages in this vein have shown me (and taught me lots - thanks to those answering), the answer is often not what I thought. >> >> Tim >> >> >

March 18, 2019

Re: [Pharo-users] Why doesn't collection have #excludes (the mirror of includes)?

by Tim Mackinnon

Thanks guys - I always learn something new from these threads. > On 17 Mar 2019, at 06:56, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > (1) As it happens, my Smalltalk library *does* have > #excludes: and #identityExcludes: > (2) The definitions are trivial. > excludes: item > ^(self includes: item) not > identityExcludes: item > ^(self identityIncludes: item) not > > If you want to execute aBlock when aString is not all zeros > and ones, just do > (aString allSatisfy: [:each | each = $0 or: [each = $1]]) > ifFalse: [aBlock value]. > or > (aString anySatisfy: [:each | each ~= $0 and: [each ~= $1]]) > ifTrue: [aBlock value]. > or > ('01' includesAll: aString) ifFalse: [aBlock value]. > > > On Sat, 16 Mar 2019 at 11:33, Tim Mackinnon <tim(a)testit.works> wrote: > Hi - in my quest to understand the edgier details of Pharo (and Smalltalk) - and driven by fresh thoughts of completing exercism exercises - I was surprised to find that there is no #excludes: operation on collection to mirror the #includes: operation? > > I was curious about this - its seems a strange omission? > > Of course I can inverse it with not, or do things a different way - but we have ifTrue: mirrored with ifFalse, empty/notEmpty so am I missing something? > > I wanted to write something like > > > aString detect: [:c | ($0 to: $1) excludes: c] ifFound: aBlock. (Evaluate a block if the string isnât all 0 and 1âs) > > > Of course I can write this as: > > (aString reject: [:c | c = $0 | c = $1)) ifNotEmpty: aBlock > > But as recent messages in this vein have shown me (and taught me lots - thanks to those answering), the answer is often not what I thought. > > Tim > >

March 18, 2019

Re: [Pharo-users] using spotter in pharo 7. but have many error.

by Sean P. DeNigris

peter yoo wrote > many error encounterd It looks like those errors are related to fonts, not spotter. Someone else can probably tell you more... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 18, 2019

Re: [Pharo-users] Pharo refactoring rewrite tool?

by Tim Mackinnon

Ah cool - that sounds like what I was looking for - will give it a spin. Thanks > On 18 Mar 2019, at 11:46, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Tim, > > Recently I've sent a PR to load MatchTool in P7, you may want to check it out: > > https://github.com/Uko/MatchTool <https://github.com/Uko/MatchTool> > > Cheers, > > HernÃ¡n > > El dom., 17 mar. 2019 11:35 p. m., Tim Mackinnon <tim(a)testit.works> escribiÃ³: > I recall there was a refactoring rewrite tool - but where is it in Pharo? Is it something you have to load separately? Or do you just copy some of the deprecated examples and do it manually? I thought there was something with a window where you typed in a rule and then it showed you what it would do? (Or was that only in Dolphin?) > > Thanks, > > Tim

March 18, 2019

Re: [Pharo-users] Test skip isn't working?

by Ben Coman

This is a tough one to consider. Dennis's position seems very reasonable, but that Vitor got stuck is an indication of something missing. Just one other option occurs to me, that a notification pops up saying "force run skipped method", but I'm not even sure that would be beneficial. cheers -ben On Mon, 18 Mar 2019 at 22:21, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > It is confusing because something unexpected and different from what is > explicitly said on code happens... I consider it an error. > > I think It should execute informing the test is skipped or don't provide > the click button at all. It took me a long time looking at skip > implementation and trying different stuff until I figure I hadn't done > anything wrong. > > On Mon, Mar 18, 2019 at 4:22 AM Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> I think it is a feature. When you click icon on a single test you >> explicitly raise a wish to run it. >> >> Ð¿Ð½, 18 Ð¼Ð°Ñ. 2019 Ð³., 1:26 Vitor Medina Cruz <vitormcruz(a)gmail.com>: >> >>> Skip only works when I run tests from class. If I click the test button >>> from the method skipped it don't work, maybe an error in calypso? >>> >>> On Sun, Mar 17, 2019 at 3:13 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> >>> wrote: >>> >>>> Hello, >>>> >>>> someTest >>>> self skip: 'some message'. >>>> >>>> rest of the test >>>> >>>> Rest of the test is being executed. There is a different woy of >>>> skipping tests? >>>> >>>> Thanks, >>>> Vitor. >>>> >>>

March 18, 2019

Re: [Pharo-users] Test skip isn't working?

by Vitor Medina Cruz

It is confusing because something unexpected and different from what is explicitly said on code happens... I consider it an error. I think It should execute informing the test is skipped or don't provide the click button at all. It took me a long time looking at skip implementation and trying different stuff until I figure I hadn't done anything wrong. On Mon, Mar 18, 2019 at 4:22 AM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I think it is a feature. When you click icon on a single test you > explicitly raise a wish to run it. > > Ð¿Ð½, 18 Ð¼Ð°Ñ. 2019 Ð³., 1:26 Vitor Medina Cruz <vitormcruz(a)gmail.com>: > >> Skip only works when I run tests from class. If I click the test button >> from the method skipped it don't work, maybe an error in calypso? >> >> On Sun, Mar 17, 2019 at 3:13 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> >>> Hello, >>> >>> someTest >>> self skip: 'some message'. >>> >>> rest of the test >>> >>> Rest of the test is being executed. There is a different woy of skipping >>> tests? >>> >>> Thanks, >>> Vitor. >>> >>

March 18, 2019

Re: [Pharo-users] Pharo refactoring rewrite tool?

by HernÃ¡n Morales Durand

Hi Tim, Recently I've sent a PR to load MatchTool in P7, you may want to check it out: https://github.com/Uko/MatchTool Cheers, HernÃ¡n El dom., 17 mar. 2019 11:35 p. m., Tim Mackinnon <tim(a)testit.works> escribiÃ³: > I recall there was a refactoring rewrite tool - but where is it in Pharo? > Is it something you have to load separately? Or do you just copy some of > the deprecated examples and do it manually? I thought there was something > with a window where you typed in a rule and then it showed you what it > would do? (Or was that only in Dolphin?) > > Thanks, > > Tim >

March 18, 2019

using spotter in pharo 7. but have many error.

by peter yoo

only spotter. not touch anything. but many error encounterd. need more package? or need update? my pharo version is this. Pharo 7.0.1 Build information: Pharo-7.0.1+build.148.sha.442fd72baccda88a9a3a72fe8158ebb31bf1b67a (64 Bit) -- http://lookandwalk.com http://looknw.com | http://onionmixer.net peter yoo(Jonghwa Yoo). ROK

March 18, 2019

ARM vm limitations ?

by Albrecht Baur

Hi, I'd like to play around with pharo on ARM devices (like a HummingBoard, the ones from ODROID or one of the beagleboards). But I am not sure if I have to take care of the ARM architecture version (ARMv6 / ARMv7 / ARMv8) when choosing my toy. I found this vm: http://files.pharo.org/vm/pharo-spur32/linux/armv6/ Is it only for armv6 like the folder name says or is ARMv7 and ARMv8 working too? Are there any limitations I should know before choosing a ARM device? Is there a vm for 64bit (aarch64)? Thanks! Albrecht

March 18, 2019

[Issue Trackker][Help Needed]: Move issues from Fogbugz to GitHub

by Marcus Denker

Hi, We should all look at the old issues: https://pharo.fogbugz.com/f/filters/57/All-newest-first <https://pharo.fogbugz.com/f/filters/57/All-newest-first> and move them to the new one: https://github.com/pharo-project/pharo/issues instead of moving them automatically, we should take the chance to clean up. Please check, first for the issues that *you* added: -> is it still relevant? ->if yes: add a new issue on GitHub ->close this issue, there is now an explicit âmoved to GitHubâ state. Marcus

March 18, 2019