March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Porting SmaCC from 1.4 to 2.0; doSilently: equivalent ?

by stephane ducasse

> > Hi, > > I'm trying to port SmaCC to 2.0 Cool can you publish it in PharoExtras? I would like to have it there + a wonderful set of tests automatically triggered on a nice integration server :) > and I'm looking for the equivalent to SystemChangeNotifier>>doSilently:. Is it SystemAnnouncer>>suspendAllWhile:? > > (doSilently: is used in SmaCC tests). > > > There is also a nice #valueWithoutNotifications in BlockClosure. > > BTW, does it make sense to port SmaCC? faster more compact > Which use case do you have in which you prefer SmaCC over say PetitParse? > I took a look few weeks ago to something done in SmaCC and it was full of ugly unmaintainable class side tablesâ¦.. you do not have to read the assembly code of your Smalltalk programs. :) Smacc represents the traditional way to build parser and it is important to also have it around and kicking. Stef

March 8, 2013

Re: [Pharo-project] Pharo Command Line

by StÃ©phane Ducasse

Because in Pharo we are doing more than talking and we value documentation â¦â¦ Yes guys you can twitt that one! :) On Mar 8, 2013, at 2:50 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Sven wrote: >> The last couple of days I have been using the new command line tools and zero conf scripts for real and I must say that I am >truly impressed and happy. >> >> The save, printVersion, eval, st, config and test handlers are a joy to work with. The terminal colours add a nice polish. > > Any documentation on it, blog posts or pharocasts available? > > Thx > Torsten > > >

March 8, 2013

Re: [Pharo-project] Pharo Command Line

by stephane ducasse

My dream is to have phash :) with a fucking cool debugger and OO abstractions and â¦. well Pharosh And we are getting slowly thereâ¦ Stef >> The last couple of days I have been using the new command line tools and zero conf scripts for real and I must say that I am truly impressed and happy. >> >> The save, printVersion, eval, st, config and test handlers are a joy to work with. The terminal colours add a nice polish. >> >> Thank you, Camillo ! > > You're welcome ;), > and I hope we can extend all of that in the future because not only do I hate bash, > I am always impressed about my total ignorance of that language! I simply don't know > how to write proper bash scripts :D > > build.sh is dead, long live the command line interface! > >

March 8, 2013

Re: [Pharo-project] Pharo Command Line

by stephane ducasse

On Mar 8, 2013, at 2:44 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > The last couple of days I have been using the new command line tools and zero conf scripts for real and I must say that I am truly impressed and happy. It is cool :) > The save, printVersion, eval, st, config and test handlers are a joy to work with. The terminal colours add a nice polish. > > Thank you, Camillo ! Yes I'm writing a chapter on them so I would like to have feedback on it ;) > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

March 8, 2013

Re: [Pharo-project] Cleanup of the Zerconf scripts

by stephane ducasse

On Mar 8, 2013, at 1:23 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > With the release of 2.0 imminent we are going to cleanup the zeroconf scripts a bit: > > - the only valid VM scripts are PharoVM, StackVM and RizelVM > - NBCogVM and CogVM scripts are going to be removed! Superb! > so if you used ciPharo20NBCogVM.sh, use ciPharo20PharoVM.sh from now on! > > I will deprecate the scripts in a first step, and fully remove them within next week. Superb! Cleaning cleaning cleaning is the only way :) > I hope this won't cause too many problems, otherwise let me know.

March 8, 2013

[Pharo-project] Pharo consultants

by StÃ©phane Ducasse

Hi guys I just got a nice chat with a cool Pharo expert (Mariano) that is doing consulting and development around Pharo and this is a cool feeling to know that smart guys in our community can find nice jobs that keeps them busy in Pharo. I think that we should market the community much more, because I think that this is important for other companies to know that they can find help with really talented people in our community. May be we should make more noise around: Pharo: a community with smart developers for cool business Stef

March 8, 2013

[Pharo-project] building traits programmatically

by Ciprian Teodorov

Hi guys, Can anyone give me some pointers on how to create traits dynamically? I have tried something like: model := RBNamespace new. model defineClass: ('Trait named: #TMyTrait uses: {} category: ''My-Tests'''). and I get a DNU: RBAddTraitChange>>superclassName Cheers, -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

March 8, 2013

Re: [Pharo-project] VM Crashes

by Eliot Miranda

List, I hope you realize I'm motivated to investigate VM crashes. Esteban reports that the VM is now more stable w.r.t. becomeForward: after I debugged load cases a couple of week ago. But I could do with some help. It really helps to be provided with an image that reproduces the bug in start-up. e.g. evaluating a doit that saves and then invokes crashing code: Smalltalk saveAs: 'crash'. Gofer it url: 'http://www.squeaksource.com/MetacelloRepository'; package: 'ConfigurationOfFFI'; load. (Smalltalk at: #ConfigurationOfFFI) project stableVersion load. This saves me a lot of time. I have a day job that does not pay me to investigate Cog crashes. Your help is most appreciated. On Fri, Mar 8, 2013 at 8:14 AM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > To join in again, my regression tests still seem to fail loading. > So it looks like a similar effect as what sven experiences! > > https://ci.inria.fr/pharo/job/Pharo-2.0-Regression-Tests/VM=PharoVM,label=m… -- best, Eliot

March 8, 2013

Re: [Pharo-project] osprocess in pharo 2.0

by David T. Lewis

On Fri, Mar 08, 2013 at 05:27:04PM +0100, Camillo Bruni wrote: > thanks, I changed it and it sort of works: https://ci.inria.fr/pharo-contribution/job/OSProcess/ > though an impressive number of 81 tests fail, that is almost 50% of all the tests. > Is that normal? > I wouldn't call in "normal", but the full test suite requires an interpreter VM on Unix. To check for failures associated with the image, as opposed to VM features, I need to run the tests on an interpreter VM. Unfortunately I cannot open a Pharo image on an interpreter VM any more, possibly due to something failing in the startUp sequence. If anyone can explain what has changed I'd appreciate the help, because I have not been able to figure it out. Dave

March 8, 2013

Re: [Pharo-project] osprocess in pharo 2.0

by David T. Lewis

On Fri, Mar 08, 2013 at 08:13:19AM -0800, Sean P. DeNigris wrote: > On Mar 8, 2013, at 3:49 AM, Camillo Bruni-3 [via Smalltalk] <ml-node+s1294792n4675680h68(a)n4.nabble.com> wrote: > > I wonder why it fails on the build-server? > It fails because ThisOSProcess class>>shutDown: includes "OSProcess accessor breakDependents", but OSProcess accessor returns nil because none of the platform packages are loaded by the 'Tests' group of ConfigurationOfOSProcess. > Thanks Sean, So I should add a nil check in the shutDown: method, right? I'll do it later tonight when I get home. Dave

March 8, 2013