December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] updating ConfigurationOfPharo

by Mariano Martinez Peck

Laurent, there is really not a problem, since beta2 is with blessing "development". This "allows" you to update versions. If the blessing would be "release" for example, I would suggest to create a new version. But since this is just an update, I would use beta2. Cheers Mariano On Tue, Dec 14, 2010 at 4:26 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Mmm, beta2 is loading well (just tests are failing). > > I think moving to a beta3 should be ok for next step, but I don't have the > last word on it :). > > Guille > > > On Mon, Dec 13, 2010 at 4:44 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Hi, >> >> I want to update ConfigurationOfPharo to include last ProfStef. Should I >> update #version12beta2 or create #version12beta3 ? >> >> Laurent Laffont >> > >

Dec. 14, 2010

Re: [Pharo-project] New SqueakSource (was good news of the year)

by Mariano Martinez Peck

I really like that ESUG is sponsoring this work, for the obvious reasons, but in addition, because: - Some people say ESUG/Pharo is "married" with seaside, which it is not. As you can see here, ESUG sponsored a development in Iliad. - Some people say ESUG is married with Pharo, but again, here you can see another example for squeak/pharo, and even more, the developers of Iliad are usually GNU Smalltalk (I think). cheers mariano On Tue, Dec 14, 2010 at 5:24 PM, Benoit St-Jean <bstjean(a)yahoo.com> wrote: > Since most "file-based languages" developers refer to the word "code", why > not simply code.world.st ? > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > > >

Dec. 14, 2010

Re: [Pharo-project] [squeak-dev] cog and crash.dmp

by Eliot Miranda

On Mon, Dec 13, 2010 at 11:44 PM, Alexander LazareviÄ <laza(a)blobworks.com>wrote: > Hi! > > Not my turf, so I'm a little puzzled! > Does the latest cog vm for windows (7) also write a crash.dmp file to the > vmpath when it crashes? The dialog says so, but I can't find the file in > that directory. I have permission to create/write files in that directory.Is > there some sort of switch/ini-Setting I have to set to make the vm dump that > file on a crash? > The Cog VMs write crash.dmp to the vm log directory which is set by primitiveSetLogDirectory. The log directory appears to default to the empty string which may default to the current directory. I'll see about trying to harmonize the behaviour with the standard VM. See the attached for an interface, but I wouldn't rush to include this in trunk yet. best Eliot > Alex > > > >

Dec. 14, 2010

Re: [Pharo-project] New SqueakSource (was good news of the year)

by Benoit St-Jean

Since most "file-based languages" developers refer to the word "code", why not simply code.world.st ? ----------------- Benoit St-Jean Yahoo! Messenger: bstjean A standpoint is an intellectual horizon of radius zero. (Albert Einstein)

Dec. 14, 2010

Re: [Pharo-project] New SqueakSource (was good news of the year)

by laurent laffont

"Monticello breaks Smalltalk systems down into their fundamental units, which are called elements" http://elements.world.st (source reminds text & files and I like that I don't have to deal with files in Smalltalk). my 2 cents. Laurent On Tue, Dec 14, 2010 at 5:11 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 14 December 2010 17:02, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > > > > Janko MivÅ¡ek wrote: > >> > >> .... > >> Geert will love a proposed link: > >> http://source.world.st :) > >> or maybe: http://code.world.st ? > >> > >> And name: SmalltalkHub, SmalltalkSource? > >> ... > >> > > > > I do like "SmalltalkSource" and any subdomain at world.st is of course > > available :) I like "st.world.st" or probaly even better "sts.world.st" > > i.e. SmallTalkSource at the World of Smalltalk > > > > src.world.st > > :) > > > > > ps. just as a side-note, "world.st" is the home of the "Smalltalk > Community" > > ... proudly sponsored by ESUG as well I may add :) > > -- > > View this message in context: > http://forum.world.st/good-news-of-the-year-tp3083142p3087370.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > >

Dec. 14, 2010

Re: [Pharo-project] New SqueakSource (was good news of the year)

by Igor Stasenko

On 14 December 2010 17:02, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > Janko MivÅ¡ek wrote: >> >> .... >> Geert will love a proposed link: >> Â Â Â Â http://source.world.st :) >> or maybe: http://code.world.st ? >> >> And name: SmalltalkHub, SmalltalkSource? >> ... >> > > I do like "SmalltalkSource" and any subdomain at world.st is of course > available :) Â I like "st.world.st" or probaly even better "sts.world.st" > i.e. SmallTalkSource at the World of Smalltalk > src.world.st :) > > ps. just as a side-note, "world.st" is the home of the "Smalltalk Community" > ... proudly sponsored by ESUG as well I may add :) > -- > View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3087370.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Best regards, Igor Stasenko AKA sig.

Dec. 14, 2010

Re: [Pharo-project] New SqueakSource (was good news of the year)

by Geert Claes

Janko MivÅ¡ek wrote: > > .... > Geert will love a proposed link: > http://source.world.st :) > or maybe: http://code.world.st ? > > And name: SmalltalkHub, SmalltalkSource? > ... > I do like "SmalltalkSource" and any subdomain at world.st is of course available :) I like "st.world.st" or probaly even better "sts.world.st" i.e. SmallTalkSource at the World of Smalltalk ps. just as a side-note, "world.st" is the home of the "Smalltalk Community" ... proudly sponsored by ESUG as well I may add :) -- View this message in context: http://forum.world.st/good-news-of-the-year-tp3083142p3087370.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 14, 2010

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Updates: Status: Invalid Comment #2 on issue 3436 by rydier: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 Yeah, clearly mixed it up with copyFrom:to:, copyAfter:, or another similar collection method.

Dec. 14, 2010

Re: [Pharo-project] Issue 3436 in pharo: #copyFrom: is broken

by pharo＠googlecode.com

Comment #1 on issue 3436 by bstj...(a)yahoo.com: #copyFrom: is broken http://code.google.com/p/pharo/issues/detail?id=3436 #copyFrom: is not intended to copy strings, it is used to copy instVars that are common to the receiver and the argument into the receiver. Behaves as expected. Perhaps the name is misleading ?!?

Dec. 14, 2010

Re: [Pharo-project] updating ConfigurationOfPharo

by Guillermo Polito

Mmm, beta2 is loading well (just tests are failing). I think moving to a beta3 should be ok for next step, but I don't have the last word on it :). Guille On Mon, Dec 13, 2010 at 4:44 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi, > > I want to update ConfigurationOfPharo to include last ProfStef. Should I > update #version12beta2 or create #version12beta3 ? > > Laurent Laffont >

Dec. 14, 2010