- Pharo-dev - lists.pharo.org

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Henrik Sperre Johansen

On 17.08.2011 22:11, stephane ducasse wrote: > Hi guys > > I would like to get a better system and I would appreciate some comments for these methods. > > Stef Execute receiving block with as many arguments as it requires. This allows us to write blocks more concisely when we are not necessarily interested in all the available arguments. #cull fills the same need as #valueWith[Possible/Enough]Args: , but does not require creating an Array with the arguments, and will raise an error if block has more arguments than provided rather than pass nil in the extraneous ones. Hence, from where the block is provided, they look almost the same, but where the block is executed, the code is usually cleaner. Cheers, Henry

Aug. 17, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by StÃ©phane Ducasse

I prefer execute :) because evaluate looks like you don't run fast and generate possibly assembly on the fly. I stopped long time ago to use evaluate because people also think that Smalltalk is slow because of that evaluation.... silly idiots but they are out there. Stef (Ze mass educator) On Aug 17, 2011, at 10:29 PM, Igor Stasenko wrote: > execute or evaluate? > > > On 17 August 2011 23:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> I wrote >> >> >> cull: anArg >> "Execute the receiver with one or zero argument. >> >> [ 1 + 2 ] cull: 5 >> returns 3 >> [ :x | 1+ 2 + x] cull: 5 >> returns 8 >> " >> ^numArgs = 0 >> ifTrue: [self value] >> ifFalse: [self value: anArg] >> >> >> >> cull: firstArg cull: secondArg >> "Execute the receiver with two or less arguments. >> >> [ 1 + 2 ] cull: 5 cull: 6 >> returns 3 >> [ :x | 1+ 2 + x] cull: 5 >> returns 8 >> [ :x | 1+ 2 + x] cull: 5 cull: 3 >> returns 8 >> [ :x : y | 1+ y + x] cull: 5 cull: 2 >> returns 8 >> " >> ^numArgs < 2 >> ifTrue: [self cull: firstArg] >> ifFalse: [self value: firstArg value: secondArg] >> >> >> cull: firstArg cull: secondArg cull: thirdArg >> "Execute the receiver with three or less arguments. Check cull:cull: for examples" >> >> ^numArgs < 3 >> ifTrue: [self cull: firstArg cull: secondArg] >> ifFalse: [self value: firstArg value: secondArg value: thirdArg] >> >> >> cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg >> "Execute the receiver with four or less arguments. Check cull:cull: for examples" >> ^numArgs < 4 >> ifTrue: [self cull: firstArg cull: secondArg cull: thirdArg] >> ifFalse: [self value: firstArg value: secondArg value: thirdArg value: fourthArg] >> >> Will add a bug entry >> >> Stef >> > > > > -- > Best regards, > Igor Stasenko AKA sig.

Aug. 17, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Igor Stasenko

this is a convenience methods On 17 August 2011 23:29, Philippe Marschall <kustos(a)gmx.net> wrote: > On 17.08.2011 22:17, StÃ©phane Ducasse wrote: >> I wrote >> >> >> cull: anArg >> Â Â Â "Execute the receiver with one or zero argument. >> >> Â Â Â [ 1 + 2 ] cull: 5 >> Â Â Â Â Â Â Â returns 3 >> Â Â Â [ :x | 1+ 2 + x] cull: 5 >> Â Â Â Â Â Â Â returns 8 >> Â Â Â " >> Â Â Â ^numArgs = 0 >> Â Â Â Â Â Â Â ifTrue: [self value] >> Â Â Â Â Â Â Â ifFalse: [self value: anArg] >> > > > So it's like #valueWithPossibleArgument:? Why do we need two methods > that do the same thing? > > Cheers > Philippe > > > -- Best regards, Igor Stasenko AKA sig.

Aug. 17, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Igor Stasenko

execute or evaluate? On 17 August 2011 23:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I wrote > > > cull: anArg > Â Â Â Â "Execute the receiver with one or zero argument. > > Â Â Â Â [ 1 + 2 ] cull: 5 > Â Â Â Â Â Â Â Â returns 3 > Â Â Â Â [ :x | 1+ 2 + x] cull: 5 > Â Â Â Â Â Â Â Â returns 8 > Â Â Â Â " > Â Â Â Â ^numArgs = 0 > Â Â Â Â Â Â Â Â ifTrue: [self value] > Â Â Â Â Â Â Â Â ifFalse: [self value: anArg] > > > > cull: firstArg cull: secondArg > Â Â Â Â "Execute the receiver with two or less arguments. > > Â Â Â Â [ 1 + 2 ] cull: 5 cull: 6 > Â Â Â Â Â Â Â Â returns 3 > Â Â Â Â [ :x | 1+ 2 + x] cull: 5 > Â Â Â Â Â Â Â Â returns 8 > Â Â Â Â [ :x | 1+ 2 + x] cull: 5 cull: 3 > Â Â Â Â Â Â Â Â returns 8 > Â Â Â Â [ :x : y | 1+ y + x] cull: 5 cull: 2 > Â Â Â Â Â Â Â Â returns 8 > Â Â Â Â " > Â Â Â Â ^numArgs < 2 > Â Â Â Â Â Â Â Â ifTrue: [self cull: firstArg] > Â Â Â Â Â Â Â Â ifFalse: [self value: firstArg value: secondArg] > > > cull: firstArg cull: secondArg cull: thirdArg > Â Â Â Â "Execute the receiver with three or less arguments. Check cull:cull: for examples" > > Â Â Â Â ^numArgs < 3 > Â Â Â Â Â Â Â Â ifTrue: [self cull: firstArg cull: secondArg] > Â Â Â Â Â Â Â Â ifFalse: [self value: firstArg value: secondArg value: thirdArg] > > > cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg > Â Â Â Â "Execute the receiver with four or less arguments. Check cull:cull: for examples" > Â Â Â Â ^numArgs < 4 > Â Â Â Â Â Â Â Â ifTrue: [self cull: firstArg cull: secondArg cull: thirdArg] > Â Â Â Â Â Â Â Â ifFalse: [self value: firstArg value: secondArg value: thirdArg value: fourthArg] > > Will add a bug entry > > Stef > -- Best regards, Igor Stasenko AKA sig.

Aug. 17, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Philippe Marschall

On 17.08.2011 22:17, StÃ©phane Ducasse wrote: > I wrote > > > cull: anArg > "Execute the receiver with one or zero argument. > > [ 1 + 2 ] cull: 5 > returns 3 > [ :x | 1+ 2 + x] cull: 5 > returns 8 > " > ^numArgs = 0 > ifTrue: [self value] > ifFalse: [self value: anArg] > So it's like #valueWithPossibleArgument:? Why do we need two methods that do the same thing? Cheers Philippe

Aug. 17, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by StÃ©phane Ducasse

I wrote cull: anArg "Execute the receiver with one or zero argument. [ 1 + 2 ] cull: 5 returns 3 [ :x | 1+ 2 + x] cull: 5 returns 8 " ^numArgs = 0 ifTrue: [self value] ifFalse: [self value: anArg] cull: firstArg cull: secondArg "Execute the receiver with two or less arguments. [ 1 + 2 ] cull: 5 cull: 6 returns 3 [ :x | 1+ 2 + x] cull: 5 returns 8 [ :x | 1+ 2 + x] cull: 5 cull: 3 returns 8 [ :x : y | 1+ y + x] cull: 5 cull: 2 returns 8 " ^numArgs < 2 ifTrue: [self cull: firstArg] ifFalse: [self value: firstArg value: secondArg] cull: firstArg cull: secondArg cull: thirdArg "Execute the receiver with three or less arguments. Check cull:cull: for examples" ^numArgs < 3 ifTrue: [self cull: firstArg cull: secondArg] ifFalse: [self value: firstArg value: secondArg value: thirdArg] cull: firstArg cull: secondArg cull: thirdArg cull: fourthArg "Execute the receiver with four or less arguments. Check cull:cull: for examples" ^numArgs < 4 ifTrue: [self cull: firstArg cull: secondArg cull: thirdArg] ifFalse: [self value: firstArg value: secondArg value: thirdArg value: fourthArg] Will add a bug entry Stef

Aug. 17, 2011

[Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by stephane ducasse

Hi guys I would like to get a better system and I would appreciate some comments for these methods. Stef

Aug. 17, 2011

Re: [Pharo-project] Squeaksource not synchronized

by Fabrizio Perin

do you want the entire folder or just the missing files? 2011/8/17 Marcus Denker <marcus.denker(a)inria.fr> > > On Aug 17, 2011, at 6:02 PM, Torsten Bergmann wrote: > > >> It seems not working. Could you please double check? I don't know how to > >> proceed. Someone have any idea? > > > > It's not there yet. Still wrong. > > > > Maybe you could delete the core/dev 1-3 mcz's on the hard disk > > and I reimport them. > > > > Yes, we can copy the package from SqueakSource, delete them there and send > them to the authors... > > Fabrizio, do you do that or should I? > > > Andreas Raab also seems to miss packages: > > > > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-August/161238.h… > > > > Bye > > T. > > -- > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > > > -- > Marcus Denker -- http://marcusdenker.de > > >

Aug. 17, 2011

Re: [Pharo-project] Policy for storing metacello configurations

by Dale Henrichs

Damien and others, I am hoping to have a set of relatively informal discussions of "Metacello and collaboration" on Saturday and Sunday at Camp Smalltalk with additional discussions throughout the week. I'll send mail to the Metacello mailing list[1] and tweet[2] about times and locations, which might end up being "meet now at the table in the lobby":). I'll also try to take notes and share info on the mailing list... If you have ideas and opinions I'm interested in hearing them, so come one up to me if the time is right we'll start an impromptu discussion group. If you won't be attending ESUG, then now would be a good time to send mail to the Metacello mailing list with your ideas and we can use them as topic in the discussions ... Dale [1] http://groups.google.com/group/metacello/ [2] http://twitter.com/#!/metacello ----- Original Message ----- | From: "Damien Pollet" <damien.pollet(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, August 17, 2011 10:34:06 AM | Subject: Re: [Pharo-project] Policy for storing metacello configurations | | On 17 August 2011 19:04, Dale Henrichs <dhenrich(a)vmware.com> wrote: | > Stef and I are going to talk at ESUG about the | > procedures/recommendations/tools for managing configurations in | > Pharo. | | Cool, I'm interested too (though probably to obsessive-compulsive to | have a useful point of view) | | > I (almost) apologize for naming the class MetacelloToolBox, but | > what do you expect from a person who makes up names all the time? | > With project names like Metacello or tODE and a blog called | > '(gem)Stone Soup' it's not always clear whether I'm making a | > mistake or a statement:) | | MetacelloToolRectangleMorph. That would have been a statement :) | | -- | Damien Pollet | type less, do more [ | ] http://people.untyped.org/damien.pollet | |

Aug. 17, 2011

Re: [Pharo-project] Policy for storing metacello configurations

by Bernat Romagosa

Great, really! :) So, ideally we'd have ONE single config repo (MetacelloRepository), and Gofer project would look there, is that it? 2011/8/17 Dale Henrichs <dhenrich(a)vmware.com> > Bernat, > > A while ago, Esteban Lorenzano released the GoferProjectLoader[1] that > extends Gofer and allows one to load configurations. For example: > > Gofer project > load: 'Seaside30'; > load: 'Pier2'. > > loads the latest version of Seaside30 and then Pier2 ... there are options > for further control ... > > By default 'Gofer project' looks in the MetacelloRepository, which works > but right now subject to problems like the original complaint that started > this thread... > > Stef and I will be talking about the process and implementation for > "...looking up which repo and version are the suitable ones" so hopefully > we'll come out of ESUG with a plan of action to take care of this problem... > > Dale > > > [1] http://forum.world.st/ANN-Gofer-Project-Loader-1-0-BETA-td1596415.html > > ----- Original Message ----- > | From: "Bernat Romagosa" <tibabenfortlapalanca(a)gmail.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Wednesday, August 17, 2011 11:30:30 AM > | Subject: Re: [Pharo-project] Policy for storing metacello configurations > | > | I'm not sure whether this is one of the goals of the community or > | whether maybe someone's already heading in this direction, but > | something like Gofer install: #myPackage that looked up which repo > | and version are the suitable ones would really rock big time. The > | apt-get of Pharo, call it... > | > | > | To go on with the apt metaphor, Gofer search: 'whatever' could return > | a list of packages the descriptions/names of which matched > | 'whatever'. > | > | > | What do you think? > | > | > | > | 2011/8/17 Johan Brichau < johan(a)inceptive.be > > | > | > | Maybe a bit of wishful thinking butâ¦ > | > | Ideally, I think of the metacellorepository as a kind of 'smart > | folder' where all metacello configurations of public repositories > | are automatically included. > | Something like a smart mail folder on mac mail. > | > | Having two locations with the same package almost always leads to > | confusion / mistakes / forgetting / etcâ¦ > | > | Would such an 'automatic' repository be possible to implement in > | squeaksource3 and/or smalltalk hub? > | > | Johan > | > | > | > | > | On 17 Aug 2011, at 20:01, StÃ©phane Ducasse wrote: > | > | > > | > The policy should be > | > - put a configurationOf in your package > | > - publish when you want a copy of it in metacellorepository > | > > | > I will sit with dale sunday because we want the "publish" to copy > | > all the dependent package also in the > | > DistributionMetacelloRepository > | > > | > On Aug 17, 2011, at 8:59 AM, Max Leske wrote: > | > > | >> I would like to complain a bit about the current way Metacello > | >> configurations are distributed in different repositories. I ended > | >> up using the wrong configuration for two different projects twice > | >> in just two days. Apart from the date in the configuration file > | >> (and possibly the version number, although that's not as > | >> reliable) there's no easy way to tell which configuration is the > | >> most recent. > | >> > | >> Some people seem to have adopted MetacelloRepository as the > | >> standard repository for all configurations, others keep the > | >> configuration for a project in the project repositories and a > | >> third group uses both repositories (where one repository contains > | >> outdated versions of courseâ¦). > | >> > | >> Can we please agree on a simple policy on where to store the > | >> configuration for a project? I am sure that this would make life > | >> easier for all of us. > | >> > | >> Cheers, > | >> Max > | > > | > > | > | > | > | > | > | > | -- > | Bernat Romagosa. > | > > -- Bernat Romagosa.

Aug. 17, 2011