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

Re: [Pharo-project] ESUG gentle actions reminder

by StÃ©phane Ducasse

I was stupid to forgot the sponsors of esug. Shame on us. But yes the sponsors are also big help in making ESUG a success. Stef On Mar 10, 2010, at 9:07 AM, Torsten Bergmann wrote: > ... wow! THANKS TO ALL PEOPLE INVOLVED IN ESUG! The most challenged one is Noury that deals with excel and finance for the others this is most of the time fun :) Without noury we are dead :) > > Bye > T. > -- > Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - > jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

[Pharo-project] ESUG gentle actions reminder

by Torsten Bergmann

... wow! THANKS TO ALL PEOPLE INVOLVED IN ESUG! Bye T. -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser

March 10, 2010

Re: [Pharo-project] CrLfFileStream class>>new?!

by Adrian Lienhard

Thanks, Henrik! I created issue http://code.google.com/p/pharo/issues/detail?id=2128 so it doesn't get lost. Cheers, Adrian On Mar 10, 2010, at 01:06 , Henrik Sperre Johansen wrote: > On 09.03.2010 21:48, StÃ©phane Ducasse wrote: >> It would be good to add that to the method and class comment. >> Henrik? >> >> Stef > Slice-CrLfFileStreamDeprecation in Inbox. > > Adds an explanation to class comment and in new method, reroutes the default-lineEnd methods, and deprecates basicNew just in case. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

Re: [Pharo-project] [update 1.1] #11255

by Adrian Lienhard

>> It seems there is a problem as cleanUp or cleanUp: are implemented in > SmalltalkImage but not in SystemDictionary...so evaluating > > Smalltalk cleanUp. > Smalltalk cleanUp: true. > > gives a DNU. > > Another question....wouldn't be a good idea to add at least a "Smalltalk > cleanUp. " in ScriptLoader >> cleanUpForRelease ??? or similar.... Yes. And when we adopt the cleanUp protocol, the stuff in cleanUpForRelease should be moved into the appropriate classes. Cheers, Adrian

March 10, 2010

Re: [Pharo-project] Full time engineer position for Pharo looking for cool engineer :)

by StÃ©phane Ducasse

Something really important that I forgot to say. Thanks to all of you that are making Pharo cool. The key point is that of course we wrote a request document (10 pages), went to meetings to understand what they wanted, rewrote the document, motivated it,... But at the end the fact that INRIA supports pharo is not because of us but because of you and the impact they see. So all the submissions, users, mailing-list traffic... counts. So just replying to emails mentioning that you use pharo to do research teach develop applications was already a good action :) Thanks since I forget to mention it. Stef

March 10, 2010

Re: [Pharo-project] CrLfFileStream class>>new?!

by StÃ©phane Ducasse

coooool ! I like to be in this community. Stef On Mar 10, 2010, at 1:06 AM, Henrik Sperre Johansen wrote: > On 09.03.2010 21:48, StÃ©phane Ducasse wrote: >> It would be good to add that to the method and class comment. >> Henrik? >> >> Stef > Slice-CrLfFileStreamDeprecation in Inbox. > > Adds an explanation to class comment and in new method, reroutes the default-lineEnd methods, and deprecates basicNew just in case. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

Re: [Pharo-project] [update 1.1] #11255

by StÃ©phane Ducasse

yeap! Closed. This was since september that this was on my todo. Miguel I added you as project committers On Mar 10, 2010, at 12:53 AM, Miguel Enrique CobÃ¡ Martinez wrote: > El mar, 09-03-2010 a las 22:40 +0100, StÃ©phane Ducasse escribiÃ³: >> 11255 >> ----- >> >> - added tests for the compiler to test shadowing of self, super, thisContext, true, false and nil. Thanks guys - we know you :) >> >> - Issue 2086: Introduce a cleanUp/cleanUp: protocol from squeak / keith idea! >> MyClass class>>cleanUp: aggressive >> This (class-side) method is called with an argument that indicates whether to do aggressive, i.e., potentially destructive cleanup. Doing aggressive cleanup will delete projects, change sets, uni-classes and more. Gentle cleanup is expected to only flush transient caches. If your class only has gentle cleanup you can simply implement >> >> MyClass class>>cleanUp >> >> By default #cleanUp: delegates to this method (similar to startUp/startUp: and shutDown/shutDown:). You can >> run cleanup by executing: >> >> Smalltalk cleanUp. >> Smalltalk cleanUp: true. >> >> Thanks luc for your analysis. After lunch in hot room is never that good for my brain :) >> > > Cool, very good. Good to see this implemented at least. > Can we then close: > > http://code.google.com/p/pharo/issues/detail?id=1778 > > as it appears to me that this solves it. > > Cheers > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

Re: [Pharo-project] [update 1.1] #11255

by StÃ©phane Ducasse

This is on purpose :) We plan to have Smalltalk -> SmalltalkImage current soon (after all the years I have been waiting for it to happen this is good to see it happening in squeak It was not top priority for pharo but on the huge todo so now we will do it). Stef > MyClass class>>cleanUp: aggressive > This (class-side) method is called with an argument that indicates whether to do aggressive, i.e., potentially destructive cleanup. Doing aggressive cleanup will delete projects, change sets, uni-classes and more. Gentle cleanup is expected to only flush transient caches. If your class only has gentle cleanup you can simply implement > > MyClass class>>cleanUp > > By default #cleanUp: delegates to this method (similar to startUp/startUp: and shutDown/shutDown:). You can > run cleanup by executing: > > Smalltalk cleanUp. > Smalltalk cleanUp: true. > > > It seems there is a problem as cleanUp or cleanUp: are implemented in SmalltalkImage but not in SystemDictionary...so evaluating > > Smalltalk cleanUp. > Smalltalk cleanUp: true. > > gives a DNU. > > Another question....wouldn't be a good idea to add at least a "Smalltalk cleanUp. " in ScriptLoader >> cleanUpForRelease ??? or similar.... > > Cheers > > Mraiano > > > > Thanks luc for your analysis. After lunch in hot room is never that good for my brain :) > > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

Re: [Pharo-project] ESUG gentle actions reminder

by StÃ©phane Ducasse

who knows? Some people with a small vision :) And may be some people may not have noticed that over the years some open source dialect got a lot out of ESUG and they could insinuate that ESUG coudl be against it. We did not put all the cost of the actions because we are not that picky but a project is about 2500 Euros, and summertalk was 1500 Euros now 2500 Euros and cleaning Squeak VM for example cost several project cost. Probably because people do not study at school history and are bad in statistics nowadays but prefer marketing :). Stef On Mar 9, 2010, at 10:57 PM, Igor Stasenko wrote: > On 9 March 2010 23:49, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Dear Smalltalkers of all dialects! >> >> In a time where we are bombarded with information and may be misinformed :), >> some of you may not notice that ESUG is doing a great job pushing Smalltalk, we thought that it is good >> to get a gentle reminder on the main actions ESUG performed in the past. http://www.esug.org >> Yes we have been busy promoting the language we all love. :) >> >> The board. >> > > I hardly believe that there is anyone who thinks that ESUG is evil :) > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 10, 2010

Re: [Pharo-project] VM crash on Windows

by Andreas Raab

Hi Bill - If you have problems like these consider cross-posting to squeak-dev or vm-dev. I only check Pharo in irregular intervals. On 3/8/2010 4:27 PM, Schwab,Wilhelm K wrote: > I am having a sudden problem with Pharo crashing on Windows - it's quitting on handling Seaside requests, and I'm getting **no** information. The VM pops up the output console, writes a lot of (probably useful) information to it, and then promptly exits. The issue you're seeing is caused by a recursive MessageNotUnderstood error. You can easily recreate this by doing the following: ((ProtoObject subclass: #Bummerator instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'Kernel-Objects') superclass: nil; new) bummer. The reason why that doesn't result in a regular crash.dmp is that the support code (which catches the crashes and writes the dump) isn't involved at all. The interpreter just quits. Contrast this with, say the result of an FFI crash: (ExternalLibraryFunction name:'' module: '' callType: 0 returnType: ExternalType void argumentTypes: #()) setHandle: ((ExternalAddress new) at: 1 put: 1; yourself); invoke This does generate a crash.dmp since the support code can catch the problem. However, to catch the former issue you can run the vm with -log: <logfile> which will contain the resulting output. > The rebuttal: if it has time/ability to write information all over part of the screen, it can open a file and make sure it leaves a trace of what happened. Right? The current vms (Windows and Linux) appear to be totally disinterested in logging crashes, and that needs to change. They do if you tell 'em to. Cheers, - Andreas

March 10, 2010