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

[Pharo-project] [Issue Tracker] Failing Tests in 2.0

by Marcus Denker

Failing test in 2.0: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=2.0%20status=F… I added all failing tests from Jenkins to the tracker. https://ci.inria.fr/pharo/view/Pharo-2.0/job/Pharo-2.0-Tests/

Jan. 28, 2013

Re: [Pharo-project] Fwd: More progress...

by Fernando Olivero

Hi Marcus, this are great news! For the less-knowledgable in OPAL, were can we read more about it? Fernando On Mon, Jan 28, 2013 at 1:15 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yes ! > > Looking forward to itâ¦ > > On 28 Jan 2013, at 13:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > â¦ maybe others are interested. > > > > Begin forwarded message: > > > >> From: Marcus Denker <marcus.denker(a)inria.fr> > >> Subject: More progress... > >> Date: January 28, 2013 1:07:19 PM GMT+01:00 > >> To: "pharo-compiler(a)lists.gforge.inria.fr" < > pharo-compiler(a)lists.gforge.inria.fr> > >> > >> Hi, > >> > >> Lots of progressâ¦ > >> > >> -> BC to Text mapping (highlighting in the debugger) > >> Instead of building the mapping in the code generator, we > instead > >> enhanced the AST and IR to have all the right information > and needed > >> mapping. > >> > >> This means: we can query the AST for "which statement > generated the byte code at offset 24?" > >> Or "which BlockNode is the one for this Context?". > >> > >> The AST combined with the Scope/Var annotations and the IR > contains all information needed, > >> and in cases where something is wrong it is easy to debug. > >> > >> -> Correct Temp Vars for Contexts (via the Scope/Var knowledge) > >> For accessing temps in blocks in the debugger. > >> Here we delegate queries to the annotated AST, this means the > Debugger uses > >> the same data structures as the compiler when it wants to > know about e.g. local temps. > >> > >> One of the nice effects is that the needed machinery is much > simpler: > >> > >> DebuggerMethodMap linesOfCode 164 > >> DebuggerMethodMapOpal linesOfCode 62 > >> > >> it is actually so simple that in a second step, there is no need > for DebuggerMethodMapOpal at all, > >> the code can be moved directly to better places (e.g. > MethodContext). Caching is handled by ASTCache. > >> > >> -> Error Handling is working. All the error handling (Parsing and > Semantic) are handled the same as > >> the old compiler. > >> > >> TODO > >> => Pass over integration. Clean up the Compiler/Parser facades. > >> (We will first have the whole thing to be compatible to the > old from the Compiler/Parser POV, > >> here more cleanups are following after we have the stuff > in the image) > >> > >> => Pass over the decompiler. BC->IR is working, IR->AST needs to > be checked. > >> > >> => Fix all showstoppers here: > http://code.google.com/p/pharo-newcompiler/issues/list > >> > >> > >> Marcus and Clement > >> > > > > >

Jan. 28, 2013

Re: [Pharo-project] Fwd: More progress...

by Sven Van Caekenberghe

Yes ! Looking forward to itâ¦ On 28 Jan 2013, at 13:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > â¦ maybe others are interested. > > Begin forwarded message: > >> From: Marcus Denker <marcus.denker(a)inria.fr> >> Subject: More progress... >> Date: January 28, 2013 1:07:19 PM GMT+01:00 >> To: "pharo-compiler(a)lists.gforge.inria.fr" <pharo-compiler(a)lists.gforge.inria.fr> >> >> Hi, >> >> Lots of progressâ¦ >> >> -> BC to Text mapping (highlighting in the debugger) >> Instead of building the mapping in the code generator, we instead >> enhanced the AST and IR to have all the right information and needed >> mapping. >> >> This means: we can query the AST for "which statement generated the byte code at offset 24?" >> Or "which BlockNode is the one for this Context?". >> >> The AST combined with the Scope/Var annotations and the IR contains all information needed, >> and in cases where something is wrong it is easy to debug. >> >> -> Correct Temp Vars for Contexts (via the Scope/Var knowledge) >> For accessing temps in blocks in the debugger. >> Here we delegate queries to the annotated AST, this means the Debugger uses >> the same data structures as the compiler when it wants to know about e.g. local temps. >> >> One of the nice effects is that the needed machinery is much simpler: >> >> DebuggerMethodMap linesOfCode 164 >> DebuggerMethodMapOpal linesOfCode 62 >> >> it is actually so simple that in a second step, there is no need for DebuggerMethodMapOpal at all, >> the code can be moved directly to better places (e.g. MethodContext). Caching is handled by ASTCache. >> >> -> Error Handling is working. All the error handling (Parsing and Semantic) are handled the same as >> the old compiler. >> >> TODO >> => Pass over integration. Clean up the Compiler/Parser facades. >> (We will first have the whole thing to be compatible to the old from the Compiler/Parser POV, >> here more cleanups are following after we have the stuff in the image) >> >> => Pass over the decompiler. BC->IR is working, IR->AST needs to be checked. >> >> => Fix all showstoppers here: http://code.google.com/p/pharo-newcompiler/issues/list >> >> >> Marcus and Clement >> >

Jan. 28, 2013

[Pharo-project] Fwd: More progress...

by Marcus Denker

â¦ maybe others are interested. Begin forwarded message: > From: Marcus Denker <marcus.denker(a)inria.fr> > Subject: More progress... > Date: January 28, 2013 1:07:19 PM GMT+01:00 > To: "pharo-compiler(a)lists.gforge.inria.fr" <pharo-compiler(a)lists.gforge.inria.fr> > > Hi, > > Lots of progressâ¦ > > -> BC to Text mapping (highlighting in the debugger) > Instead of building the mapping in the code generator, we instead > enhanced the AST and IR to have all the right information and needed > mapping. > > This means: we can query the AST for "which statement generated the byte code at offset 24?" > Or "which BlockNode is the one for this Context?". > > The AST combined with the Scope/Var annotations and the IR contains all information needed, > and in cases where something is wrong it is easy to debug. > > -> Correct Temp Vars for Contexts (via the Scope/Var knowledge) > For accessing temps in blocks in the debugger. > Here we delegate queries to the annotated AST, this means the Debugger uses > the same data structures as the compiler when it wants to know about e.g. local temps. > > One of the nice effects is that the needed machinery is much simpler: > > DebuggerMethodMap linesOfCode 164 > DebuggerMethodMapOpal linesOfCode 62 > > it is actually so simple that in a second step, there is no need for DebuggerMethodMapOpal at all, > the code can be moved directly to better places (e.g. MethodContext). Caching is handled by ASTCache. > > -> Error Handling is working. All the error handling (Parsing and Semantic) are handled the same as > the old compiler. > > TODO > => Pass over integration. Clean up the Compiler/Parser facades. > (We will first have the whole thing to be compatible to the old from the Compiler/Parser POV, > here more cleanups are following after we have the stuff in the image) > > => Pass over the decompiler. BC->IR is working, IR->AST needs to be checked. > > => Fix all showstoppers here: http://code.google.com/p/pharo-newcompiler/issues/list > > > Marcus and Clement >

Jan. 28, 2013

[Pharo-project] [update 2.0] #20493

by Marcus Denker

20493 ----- Issue 7336: ReleaseTest is run double http://code.google.com/p/pharo/issues/detail?id=7336 Issue 7310: PickListModel should be improved http://code.google.com/p/pharo/issues/detail?id=7310 Postscript: SystemNavigation new instanceSideMethodsWithNilKeyInLastLiteral do: [ :thisShouldNotBeAStringButAMethod | | method classAndSelector | classAndSelector := ' ' split: thisShouldNotBeAStringButAMethod. method := (Smalltalk at: classAndSelector first asSymbol) methodNamed: classAndSelector second asSymbol. method recompile. ]. Diff information: http://ss3.gemstone.com/ss/Pharo20/Tests-MarcusDenker.495.diff http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.83.diff http://ss3.gemstone.com/ss/Pharo20/RPackage-Tests-MarcusDenker.105.diff

Jan. 28, 2013

Re: [Pharo-project] looking for a poll service?

by Damien Cassou

On Sun, Jan 27, 2013 at 1:46 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > we want to do a poll for two options for the pharo conference so do you know a free service for organizing that? https://doodle.com -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 28, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Ben Coman

Sean P. DeNigris wrote: > StÃ©phane Ducasse wrote > >> On Jan 27, 2013, at 9:42 AM, Esteban Lorenzano wrote: >> >> >>> so f***ing cool! >>> >> +1 >> I love to see more and more of these connections to the outside world. >> > > +1 & +1 :) > > > > -- > View this message in context: http://forum.world.st/Update-Zinc-SSO-now-supports-Dropbox-tp4665692p466576… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > And I get 50GB free space with my Samsung phone. :) :)

Jan. 28, 2013

Re: [Pharo-project] [Update] Zinc-SSO now supports Dropbox !

by Sean P. DeNigris

StÃ©phane Ducasse wrote > On Jan 27, 2013, at 9:42 AM, Esteban Lorenzano wrote: > >> so f***ing cool! > > +1 > I love to see more and more of these connections to the outside world. +1 & +1 :) -- View this message in context: http://forum.world.st/Update-Zinc-SSO-now-supports-Dropbox-tp4665692p466576… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2013

[Pharo-project] how to specify the loader type of a metacello project?

by StÃ©phane Ducasse

Hi Is there a way to specify the equivalent of project loadType: #'atomic'. at the level of an expression such as: (ConfigurationOfMoose project version: '4.7-flat') load while this loadType propagated to the projects? I saw that on a MetacelloMCVersion that there is a loaderPolicy instance variables and setters but there is no comment I have no idea what it is. It would be good to comment for real classes of the infrastructure we use. Of course MetacelloLoaderPolicy is not commented either. Sad. So apparently a MetacelloLoaderPolicy hold a loadDirective which can be a MetacelloLinearLoadDirective Stef

Jan. 28, 2013

[Pharo-project] NativeBoost linux 8 byte structures

by Ciprian Teodorov

Hi Guys, Today I wanted to test my TalkFFI project on linux, and I run into some NB issue. It seems that the VM crashes when trying to invoke a function returning a 8 byte structure. I have tried with 4 bytes structure and I get some bogus data but no crash with 12 bytes structure it seems to work... Attached to this mail you will find a simple test case. the c file I have compiled with: gcc -g -fPIC -Wall -c -m32 strreturn.c gcc -shared -g -Wl,-soname,libret.so.1 -o libret.so -m32 strreturn.o -lc 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

Jan. 27, 2013