October 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fuel for Squeak stupid questions

by Edgar J. De Cleene

On 10/15/12 5:10 PM, "Max Leske" <maxleske(a)gmail.com> wrote: > Hey Edgar > > I checked the Fuel tests in a 4.4 image and there are no differences to the > 4.3 image. > If you still have that problem with the failing Date test then you probably > have an issue with the code you loaded in addition. One package that would > break that test is PostgresV2 because that packages overrides #year:month:day: > in Date and DateAndTime. > > Cheers, > Max I re check, do not remember any I made change Date. Thanks Edgar

Oct. 15, 2012

Re: [Pharo-project] Fuel for Squeak stupid questions

by Max Leske

Hey Edgar I checked the Fuel tests in a 4.4 image and there are no differences to the 4.3 image. If you still have that problem with the failing Date test then you probably have an issue with the code you loaded in addition. One package that would break that test is PostgresV2 because that packages overrides #year:month:day: in Date and DateAndTime. Cheers, Max On 12.10.2012, at 08:33, Max Leske <maxleske(a)gmail.com> wrote: > Thanks Edgar. Much appreciated. > > > On 11.10.2012, at 21:14, Edgar J. De Cleene <edgardec2005(a)gmail.com> wrote: > >> >> >> >> On 10/11/12 12:53 PM, "Max Leske" <maxleske(a)gmail.com> wrote: >> >>> Ah! >>> >>> Could you try the Date fix I proposed in a 4.3 image? >>> >>> BTW I'm working on fixing the other failing tests (for 4.3) aswell. >>> >>> Cheers, >>> Max >> >> You was right, some changed recently in Squeak as 4.3 11860 (fresh unzipped) >> do not fail the two test of Date, the rest is same as 4.4 >> >> You only need fileIn TClassAndTraitDescription from Pharo when Monticello >> complains >> >> Edgar >> >> >> >

Oct. 15, 2012

[Pharo-project] A trend and an unfair comparison about js everywhere

by sebastian＠flowingconcept.com

Hi guys, all comparisons are unfair I know but this is only to make you guy aware of this (please ignore if you're already). Here is the thing: The Jeff Bezos' Electricity Metaphor: http://www.ted.com/talks/jeff_bezos_on_the_next_web_innovation.html Makes (probably) any smalltalker remember the Alan Kay's talk about having in the internet an IP for every object and spectacular computer science ideas like that. The js everywhere trend makes a lot of sense. Once it achieves critical mass it might tempt intel and friends to do some hardware accelerator for js VM's. Who knows. We have a long way to go but, in the meantime, all js staked frameworks make a lot of sense and WILL get traction because of that. Example: http://www.wakanda.org/ A talk here: https://vimeo.com/31603156 So.. the unfair question here would be: What we'll have to match that competitiveness? sebastian o/ PS: Pharo + WebSockets + Amber sounds in that line doesn't?

Oct. 15, 2012

Re: [Pharo-project] [Moose-dev] How to export multiple Pharo packages to VW

by Dale Henrichs

Stephan, You should be able to use FileTree[1] to export data from Pharo and then use STIG[2] to import the data into VW ... I would use git to manage the repository and create a VW branch to manage your VW-specific changes ... you will likely need to hand massage the code base to get it to load into VW, but given that you're dealing with text files, that's doable ... I haven't had time to experiment directly with this path, but it is intended to work and you should file issues with both projects if you run into issues ... at ESUG this year we talked about some new features of the Cypress format[3] that would make porting easier but they haven't been implemented yet ... Dale [1] https://github.com/dalehenrich/filetree [2] https://github.com/CampSmalltalk/STIG [3] https://github.com/CampSmalltalk/Cypress ----- Original Message ----- | From: "Stephan Eggermont" <stephane(a)xs4all.nl> | To: "Moose-related development" <moose-dev(a)iam.unibe.ch>, "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> | Sent: Monday, October 15, 2012 7:50:18 AM | Subject: [Moose-dev] How to export multiple Pharo packages to VW | | The VW5PackageExporter allows the exporting of a package to the VW | xml based fileout format. | I've adapted the code to be less Seaside-specific, and am now able to | export one package (Parasol-Core). | If I try to export another package (Parasol-Tests), which depends on | the earlier one, it fails to load. | It can't resolve the dependency to a superclass defined in | Parasol-Core. | I've seen that Roassal puts all Pharo packages into one VW package. | That would work, but is not very | nice. A package in VW doesn't seem to register its dependencies in a | fileout. Would creating a parcel | help, or should I try something on basis of RPackage? | | Stephan | | | _______________________________________________ | Moose-dev mailing list | Moose-dev(a)iam.unibe.ch | https://www.iam.unibe.ch/mailman/listinfo/moose-dev |

Oct. 15, 2012

Re: [Pharo-project] Do you know any code that can be better understood with its test?

by StÃ©phane Ducasse

On Oct 15, 2012, at 7:25 PM, Frank Shearar wrote: > On 13 October 2012 17:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Frank >> >> I was asked to do a keynote to master, phd student and other and I would like to show them that with the right >> tool we can do some powerful abstractions. >> >> I'm thinking showing them >> thisContext use for haltIf >> on:fork: example > > I don't see a #haltIf: in my Pharo 2.0 image (but it's well out of > date, and I'm still waiting for the update to finish) but I imagine it > would evaluate a block and when that block returns true, uses > thisContext sender (sender ...) to drop you into the right context? haltIf: condition â¦. haltIfCallChainContains: aSelector | cntxt | cntxt := thisContext. [cntxt sender isNil] whileFalse: [ cntxt := cntxt sender. (cntxt selector = aSelector) ifTrue: [self signal]]. > >> do you have idea? >> Should I look (I will ;)) look at Control and DynamicVariable? >> Do you have other idea? > > I think thisContext is an excellent jumping board into a great many > things. http://www.mirandabanda.org/cogblog/2009/01/14/under-cover-contexts-and-the… > has a lovely paragraph: > > "Contexts are fabulous weapons, even better programming building > blocks, and horribly expensive. How do I love contexts? Let me count > the waysâ¦ > > Contexts mean Smalltalk has had edit-and-continue debugging since the 1970â²s. > Contexts allow the implemention of an exception system with no > additional support from the virtual machine. > Contexts allow the implemention of dynamic binding, co-routines, > tail-recursion-elimination and backtracking with no additional support > from the virtual machine. > Contexts enable process persistence and migration. > Contexts allow implementation of continuations (full, > delimited/partial or otherwise) without additional VM support (and > hence the Seaside web framework). > Contexts are consistent (consistent) with the rest of the âobjects all > the way downâ system, providing activations as first-class objects. > Because theyâre there." Yes I read that a while ago. > > frank > >> Stef >> >> On Oct 13, 2012, at 5:54 PM, Frank Shearar wrote: >> >>> On 13 October 2012 15:47, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>>> I'm looking for a piece of code that is hard to understand by looking >>>> at the source code but which has unit tests that help understanding >>>> the behavior. >>>> >>>> Do you have any idea? >>> >>> http://ss3.gemstone.com/ss/Control/ has tests for delimited dynamic >>> variables. The idea's not terribly complicated - close over a variable >>> and use resumable exceptions to refer to it or change it - but if you >>> don't have that in-a-nutshell idea in your head it can look a bit >>> strange. But the tests in ControlTests' DelimitedDynamicVariableTest >>> show quite clearly how dynamic binding works. >>> >>> (The delimited part probably won't make a lot of sense until one's >>> managed to wrap one's head around control operators - shift, in this >>> case - so the nice interaction between the delimited continuations and >>> the delimited dynamic variables might be lost on a newbie.) >>> >>> frank >>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Success is the ability to go from one failure to another without >>>> losing enthusiasm." >>>> Winston Churchill >>>> >>> >> >> >

Oct. 15, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 412 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 15, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 412 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 15, 2012

[Pharo-project] pharo-2.0-tests Â» linux - Build # 412 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 15, 2012

Re: [Pharo-project] Do you know any code that can be better understood with its test?

by Frank Shearar

On 13 October 2012 17:05, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Frank > > I was asked to do a keynote to master, phd student and other and I would like to show them that with the right > tool we can do some powerful abstractions. > > I'm thinking showing them > thisContext use for haltIf > on:fork: example I don't see a #haltIf: in my Pharo 2.0 image (but it's well out of date, and I'm still waiting for the update to finish) but I imagine it would evaluate a block and when that block returns true, uses thisContext sender (sender ...) to drop you into the right context? > do you have idea? > Should I look (I will ;)) look at Control and DynamicVariable? > Do you have other idea? I think thisContext is an excellent jumping board into a great many things. http://www.mirandabanda.org/cogblog/2009/01/14/under-cover-contexts-and-the… has a lovely paragraph: "Contexts are fabulous weapons, even better programming building blocks, and horribly expensive. How do I love contexts? Let me count the waysâ¦ Contexts mean Smalltalk has had edit-and-continue debugging since the 1970â²s. Contexts allow the implemention of an exception system with no additional support from the virtual machine. Contexts allow the implemention of dynamic binding, co-routines, tail-recursion-elimination and backtracking with no additional support from the virtual machine. Contexts enable process persistence and migration. Contexts allow implementation of continuations (full, delimited/partial or otherwise) without additional VM support (and hence the Seaside web framework). Contexts are consistent (consistent) with the rest of the âobjects all the way downâ system, providing activations as first-class objects. Because theyâre there." frank > Stef > > On Oct 13, 2012, at 5:54 PM, Frank Shearar wrote: > >> On 13 October 2012 15:47, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>> I'm looking for a piece of code that is hard to understand by looking >>> at the source code but which has unit tests that help understanding >>> the behavior. >>> >>> Do you have any idea? >> >> http://ss3.gemstone.com/ss/Control/ has tests for delimited dynamic >> variables. The idea's not terribly complicated - close over a variable >> and use resumable exceptions to refer to it or change it - but if you >> don't have that in-a-nutshell idea in your head it can look a bit >> strange. But the tests in ControlTests' DelimitedDynamicVariableTest >> show quite clearly how dynamic binding works. >> >> (The delimited part probably won't make a lot of sense until one's >> managed to wrap one's head around control operators - shift, in this >> case - so the nice interaction between the delimited continuations and >> the delimited dynamic variables might be lost on a newbie.) >> >> frank >> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> > >

Oct. 15, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 411 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 15, 2012