February 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] Call for Pharo Support **important**

by StÃ©phane Ducasse

On Feb 19, 2011, at 5:35 AM, Krishsmalltalk wrote: > Count me in. Excellent! > What is the formality in sign n dispatch of the letter just sign it and scanned/fax it to me. > > Sudhakar krishnamachari > > Extn 91-40403012 > Cell 9902104814 > > > > On Feb 18, 2011, at 1:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi davorin >> It says that you would consider paying a membership if this one is ok for you but that the membership >> would have to be clear. So this is just a letter of support. Your are not tying yourself. >> We will decide together the model because we should like that everybody can contribute. >> >> Now for us this is an important tool because we can seize the community to see if we could collect >> money to pay an engineer like igor full-time, half time.... >> >> Stef >> >> >>> I am not expert in legalize, does signing of this letter imply some >>> financial commitment on part of the signer, or it is just "Pharo is >>> great and we would like to use it" kind of letter? >>> >>> Many thanks! >>> >>> Davorin Rusevljan >>> http://www.cloud208.com/ >> >> >

Feb. 19, 2011

Re: [Pharo-project] Need your point of view on FSPath * and others

by StÃ©phane Ducasse

On Feb 19, 2011, at 2:24 PM, Schwab,Wilhelm K wrote: > Stef, > > I am not sure that #* would be all that confusing: I tend not to multiply path names all that often :) However, your question is well taken. How about #any or #all? but any or all do not really have more sense. > Attached are some methods that I use to ease the transition from Dolphin. Most of the calling code needs to be modified anyway (to change to Linux conventions), thanks I will have a look. > but at least the protocol is familiar. If I were starting over, I might reify paths and define #, to concatenate them. > > Bill > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] > Sent: Friday, February 18, 2011 5:40 PM > To: Colin Putney > Cc: Pharo Development > Subject: [Pharo-project] Need your point of view on FSPath * and others > > Colin > > I'm continuing adding comments to FS. > 1- A question about > > FSPath class>>* aString > > ^ self with: aString > > I would like to deprecated FSPath class>>* and use with: since this is the message > and > > What do you think? > I really prefer for static analysis point of view not to pollute numerical behavior with others. > Avoiding ad-hoc polymorphism will help us to build static checker in the future. > > > 2- Then I was wondering if it would not be good to have validating creation methods > > (FSPath * 'parent/child/') isRelative > true > (FSPath * '/parent/child/') isAbsolute > false > because the string is not checked > FSPath * '/parejhkjhhg %% ^%$%^(%$546547675 nt??child/' > > I saw that there is > readFrom: aStream delimiter: aCharacter > > so I created an unchecking instance creation category and I added with: and * in it. > And added comments > > 3- Then finally the following confuses me > > (FSPath with: 'parent/child/') isRelative true > (FSPath with: '/parent/child/') isRelative true > (FSPath with: '') isRelative false > > Either with: create relative path or isRelative is not consistent. > If with: creates relative path then the last one should be true > or isRelative should return false on the second one. ? > > 4 - about FSPath root > we have > > root > "Return the relative root path" > ^ self with: '' > > FSPath root > returns / > and I like that > > Now what about defining root as > > root > ^ self with: '/' > > It would be more consistent. Now it breaks everything. So I did not do it :) > > > > May be I'm tired after 4 ours teaching and 6 hours train. > > > > Thanks for your time > > Stef > <File class-file name manipulation.st>

Feb. 19, 2011

Re: [Pharo-project] Pharo 1.2 virtual sprint

by csrabak＠bol.com.br

Motivation is 100% available, but the time of day for this part of World is not amenable... Em 19/02/2011 06:46, Serge Stinckwich < serge.stinckwich(a)gmail.com > escreveu: No one seems to be motivated to have a virtual sprint to release Pharo 1.2 ? On Wed, Feb 16, 2011 at 1:28 PM, laurent laffont wrote: > > On Wed, Feb 16, 2011 at 3:28 AM, Serge Stinckwich > wrote: >> >> Launch a doodle for a day long virtual sprint all over the world ;-) > > > http://www.doodle.com/byvynpkmm87hc3x8 > Laurent. > >> >> On Wed, Feb 16, 2011 at 4:54 AM, laurent laffont >> wrote: >> > Which day you prefer ? >> > Laurent >> > On Tue, Feb 15, 2011 at 10:00 AM, StÃ©phane Ducasse >> > wrote: >> >> >> >> If there is internet connection where I will be hacking with alain we >> >> can >> >> participate :). >> >> >> >> Stef >> >> >> >> On Feb 14, 2011, at 10:01 PM, laurent laffont wrote: >> >> >> >> > Could we organize a Pharo 1.2 virtual sprint over IRC to resolve, >> >> > kill, >> >> > eleminate, eradicate, destroy remaining issues ? and learn together >> >> > too. >> >> > >> >> > I can do this next week from monday to wednesday evening (France time >> >> > zone). >> >> > >> >> > Laurent >> >> >> >> >> >> >> > >> > >> >> >> >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Feb. 19, 2011

Re: [Pharo-project] Hudson builds are cool

by Tudor Girba

Sounds cool! I will look into it. Cheers, Doru On 19 Feb 2011, at 19:24, Igor Stasenko wrote: > On 19 February 2011 18:19, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> Hi Marcus, >> >> Is it possible to make the latest vm executables available over http? Like that we can use them in the Moose builds as well. >> > They are available. > > https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Unix%201.3/lastSu… > > https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Stack%20VM%20Unix/lastS… > > except that they are currently disabled, because we're lacking free > space on server :) > > The configurations is not perfect. And they are not packaged > similarily to original build. It is just a single directory with all > binaries (VM and libs). >> Cheers, >> Doru >> >> >> On 19 Feb 2011, at 17:59, Marcus Denker wrote: >> >>> >>> On Feb 19, 2011, at 1:03 AM, Miguel CobÃ¡ wrote: >>> >>>> I haven't had time to use Pharo 1.2 from Hudson until now. All I have to >>>> say is: amazing work (or job :) >>>> >>> We need to update the vms used for the build... will do that at some point >>> next week when back home. >>> >>> Marcus >>> >>> -- >>> Marcus Denker -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Every successful trip needs a suitable vehicle." >> >> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "What we can governs what we wish."

Feb. 19, 2011

Re: [Pharo-project] Hudson builds are cool

by Igor Stasenko

On 19 February 2011 18:19, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Marcus, > > Is it possible to make the latest vm executables available over http? Like that we can use them in the Moose builds as well. > They are available. https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Unix%201.3/lastSu… https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Stack%20VM%20Unix/lastS… except that they are currently disabled, because we're lacking free space on server :) The configurations is not perfect. And they are not packaged similarily to original build. It is just a single directory with all binaries (VM and libs). > Cheers, > Doru > > > On 19 Feb 2011, at 17:59, Marcus Denker wrote: > >> >> On Feb 19, 2011, at 1:03 AM, Miguel CobÃ¡ wrote: >> >>> I haven't had time to use Pharo 1.2 from Hudson until now. All I have to >>> say is: amazing work (or job :) >>> >> We need to update the vms used for the build... will do that at some point >> next week when back home. >> >> Â Â Â Marcus >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> > > -- > www.tudorgirba.com > > "Every successful trip needs a suitable vehicle." > > > > > > -- Best regards, Igor Stasenko AKA sig.

Feb. 19, 2011

Re: [Pharo-project] Hudson builds are cool

by Tudor Girba

Hi Marcus, Is it possible to make the latest vm executables available over http? Like that we can use them in the Moose builds as well. Cheers, Doru On 19 Feb 2011, at 17:59, Marcus Denker wrote: > > On Feb 19, 2011, at 1:03 AM, Miguel CobÃ¡ wrote: > >> I haven't had time to use Pharo 1.2 from Hudson until now. All I have to >> say is: amazing work (or job :) >> > We need to update the vms used for the build... will do that at some point > next week when back home. > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

Feb. 19, 2011

Re: [Pharo-project] Hudson builds are cool

by Marcus Denker

On Feb 19, 2011, at 1:03 AM, Miguel CobÃ¡ wrote: > I haven't had time to use Pharo 1.2 from Hudson until now. All I have to > say is: amazing work (or job :) > We need to update the vms used for the build... will do that at some point next week when back home. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 19, 2011

Re: [Pharo-project] [ANN] ConfigurationOfOSProcess with symbolic versions

by Miguel CobÃ¡

Also tested on - Squeak 4.2 All in One, Squeak image 10966 190 run, 189 passes, 0 expected failures, 1 failures, 0 errors, 0 unexpected passes On UnixProcessUnixFileLockingTestCase>>#testCooperatingProcess04 Cheer El sÃ¡b, 19-02-2011 a las 08:50 -0500, David T. Lewis escribiÃ³: > Thank you Miguel! > > Dave > > On Sat, Feb 19, 2011 at 03:00:23AM -0600, Miguel Cob? wrote: > > Hi all, > > > > I have updated the Metacello configuration for OSProcess. > > > > Changes > > ------- > > > > - Uses symbolic versions > > - Adds support for release 4.4.0 of OSProcess > > - Applies MetacelloToolBox validations to the old versions of the > > configuration and corrects them > > > > Install > > -------- > > > > In a PharoCore image evaluate in a workspace: > > > > Gofer it > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfOSProcess'; > > load. > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > > #stable) load. > > > > This will install the stable version for the platform you are installing > > to. This is using symbolic versions and permits to rely on the > > maintainers to specify the stable version (4.3.11, 4.3.12, 4.4.0) for a > > given platform version (PharoCore 1.1.1, PharoCore 1.2). > > > > Other versions and groups > > --------------------------- > > > > To load older versions: > > > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > > '4.3.11') load. > > > > To load other groups: > > > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > > #stable) load: 'Tests'. > > > > or > > > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > > '4.3.11') load: 'Tests'. > > > > > > Platforms > > ---------- > > > > This was tested on > > > > - PharoCore 1.1.1 > > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > > unexpected passes > > > > - PharoCore 1.2 (build #199 from Hudson) > > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > > unexpected passes > > > > P.S. I'm cross-posting to pharo and metacello lists but I don't know > > what is the correct way to announce a new configuration. Advise? > > > > Enjoy! > > -- > > Miguel Cob?? > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

Feb. 19, 2011

Re: [Pharo-project] [ANN] ConfigurationOfOSProcess with symbolic versions

by David T. Lewis

Thank you Miguel! Dave On Sat, Feb 19, 2011 at 03:00:23AM -0600, Miguel Cob? wrote: > Hi all, > > I have updated the Metacello configuration for OSProcess. > > Changes > ------- > > - Uses symbolic versions > - Adds support for release 4.4.0 of OSProcess > - Applies MetacelloToolBox validations to the old versions of the > configuration and corrects them > > Install > -------- > > In a PharoCore image evaluate in a workspace: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOSProcess'; > load. > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > #stable) load. > > This will install the stable version for the platform you are installing > to. This is using symbolic versions and permits to rely on the > maintainers to specify the stable version (4.3.11, 4.3.12, 4.4.0) for a > given platform version (PharoCore 1.1.1, PharoCore 1.2). > > Other versions and groups > --------------------------- > > To load older versions: > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > '4.3.11') load. > > To load other groups: > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > #stable) load: 'Tests'. > > or > > ((Smalltalk globals at: #ConfigurationOfOSProcess) project version: > '4.3.11') load: 'Tests'. > > > Platforms > ---------- > > This was tested on > > - PharoCore 1.1.1 > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes > > - PharoCore 1.2 (build #199 from Hudson) > 190 run, 190 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes > > P.S. I'm cross-posting to pharo and metacello lists but I don't know > what is the correct way to announce a new configuration. Advise? > > Enjoy! > -- > Miguel Cob?? > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > >

Feb. 19, 2011

Re: [Pharo-project] Need your point of view on FSPath * and others

by Schwab,Wilhelm K

Stef, I am not sure that #* would be all that confusing: I tend not to multiply path names all that often :) However, your question is well taken. How about #any or #all? Attached are some methods that I use to ease the transition from Dolphin. Most of the calling code needs to be modified anyway (to change to Linux conventions), but at least the protocol is familiar. If I were starting over, I might reify paths and define #, to concatenate them. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Friday, February 18, 2011 5:40 PM To: Colin Putney Cc: Pharo Development Subject: [Pharo-project] Need your point of view on FSPath * and others Colin I'm continuing adding comments to FS. 1- A question about FSPath class>>* aString ^ self with: aString I would like to deprecated FSPath class>>* and use with: since this is the message and What do you think? I really prefer for static analysis point of view not to pollute numerical behavior with others. Avoiding ad-hoc polymorphism will help us to build static checker in the future. 2- Then I was wondering if it would not be good to have validating creation methods (FSPath * 'parent/child/') isRelative true (FSPath * '/parent/child/') isAbsolute false because the string is not checked FSPath * '/parejhkjhhg %% ^%$%^(%$546547675 nt??child/' I saw that there is readFrom: aStream delimiter: aCharacter so I created an unchecking instance creation category and I added with: and * in it. And added comments 3- Then finally the following confuses me (FSPath with: 'parent/child/') isRelative true (FSPath with: '/parent/child/') isRelative true (FSPath with: '') isRelative false Either with: create relative path or isRelative is not consistent. If with: creates relative path then the last one should be true or isRelative should return false on the second one. ? 4 - about FSPath root we have root "Return the relative root path" ^ self with: '' FSPath root returns / and I like that Now what about defining root as root ^ self with: '/' It would be more consistent. Now it breaks everything. So I did not do it :) May be I'm tired after 4 ours teaching and 6 hours train. Thanks for your time Stef

Feb. 19, 2011