- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Opal ?

by Jean Baptiste Arnaud

ok On Jun 21, 2012, at 2:28 PM, Marcus Denker wrote: > > On Jun 21, 2012, at 2:22 PM, Damien Cassou wrote: > >> On Thu, Jun 21, 2012 at 2:01 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal >>> compiler. So, how do I load Opal in a Pharo 1.4 image ? >> >> I think it is there: >> http://www.squeaksource.com/OpalCompiler >> > > There is a problem: this is not finished. The problem is that it is not really useful right now. As I understand (stop me if i am wrong) , it doesn't really matters, the idea is to put annotation on an ast for inject code. I think it is usable in state for that use. Maybe not for full remplacement of the current compiler. But i thinks, it is painless to implement with opal comparing to the energy needed for change the old one. > And the current work is done on top of 2.0, this you can find here: > > http://smalltalkhub.com/#!/~MarcusDenker/Opal > > with the jenkins here: > > https://ci.lille.inria.fr/pharo/job/OpalCompiler/ > > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > > Best Regards Jean Baptiste Arnaud jbaptiste.arnaud(a)gmail.com

June 21, 2012

Re: [Pharo-project] Array size in inspector

by Ben Coman

Perhaps someone could update the mailing list page to mention StackOverflow. http://lists.gforge.inria.fr/mailman/listinfo/pharo-project Sean P. DeNigris wrote: > Davide Varvello wrote > >> Thanks Sean, >> Sorry for the wrong list >> >> > > No problem. We're just trying to make sure that all questions get answered, > without overflowing the devs' mailboxes. > > -- > View this message in context: http://forum.world.st/Array-size-in-inspector-tp4635484p4635865.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > >

June 21, 2012

Re: [Pharo-project] Opal ?

by Benjamin

Why is this example bad ? Ben On Jun 21, 2012, at 2:40 PM, Jean Baptiste Arnaud wrote: > hi. > JB ^^ > You can execute this code for install: > > Gofer new > squeaksource: 'OpalCompiler'; > package:'ConfigurationOfOpalCompiler'; > load. > > (Smalltalk at: #ConfigurationOfOpalCompiler) load. > > A bad example : an instance of OCClosureCompiler will return you the method node. > OCClosureCompiler new compile: 'selector > ^1+1' in: TestObject classified: 'examples' notifying: nil ifFail: []. > > For put annotation on AST maybe marcus can explain better than me. > > > > > > On Jun 21, 2012, at 2:01 PM, Goubier Thierry wrote: > >> Hi, >> >> I'd like to port an old smalltalk code tracer framework of mine to Pharo (was developped on the VisualWorks compiler) and I didn't manage to port it easily on the Pharo smalltalk compiler. >> >> I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal compiler. So, how do I load Opal in a Pharo 1.4 image ? >> >> Thanks, >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > >

June 21, 2012

Re: [Pharo-project] Opal ?

by Jean Baptiste Arnaud

hi. JB ^^ You can execute this code for install: Gofer new squeaksource: 'OpalCompiler'; package:'ConfigurationOfOpalCompiler'; load. (Smalltalk at: #ConfigurationOfOpalCompiler) load. A bad example : an instance of OCClosureCompiler will return you the method node. OCClosureCompiler new compile: 'selector ^1+1' in: TestObject classified: 'examples' notifying: nil ifFail: []. For put annotation on AST maybe marcus can explain better than me. On Jun 21, 2012, at 2:01 PM, Goubier Thierry wrote: > Hi, > > I'd like to port an old smalltalk code tracer framework of mine to Pharo (was developped on the VisualWorks compiler) and I didn't manage to port it easily on the Pharo smalltalk compiler. > > I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal compiler. So, how do I load Opal in a Pharo 1.4 image ? > > Thanks, > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > Best Regards Jean Baptiste Arnaud jbaptiste.arnaud(a)gmail.com

June 21, 2012

Re: [Pharo-project] Opal ?

by Marcus Denker

On Jun 21, 2012, at 2:22 PM, Damien Cassou wrote: > On Thu, Jun 21, 2012 at 2:01 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal >> compiler. So, how do I load Opal in a Pharo 1.4 image ? > > I think it is there: > http://www.squeaksource.com/OpalCompiler > There is a problem: this is not finished. The problem is that it is not really useful right now. And the current work is done on top of 2.0, this you can find here: http://smalltalkhub.com/#!/~MarcusDenker/Opal with the jenkins here: https://ci.lille.inria.fr/pharo/job/OpalCompiler/ Marcus -- Marcus Denker -- http://marcusdenker.de

June 21, 2012

Re: [Pharo-project] Array size in inspector

by Sean P. DeNigris

Davide Varvello wrote > > Thanks Sean, > Sorry for the wrong list > No problem. We're just trying to make sure that all questions get answered, without overflowing the devs' mailboxes. -- View this message in context: http://forum.world.st/Array-size-in-inspector-tp4635484p4635865.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 21, 2012

Re: [Pharo-project] Opal ?

by Damien Cassou

On Thu, Jun 21, 2012 at 2:01 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal > compiler. So, how do I load Opal in a Pharo 1.4 image ? I think it is there: http://www.squeaksource.com/OpalCompiler -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 21, 2012

[Pharo-project] Opal ?

by Goubier Thierry

Hi, I'd like to port an old smalltalk code tracer framework of mine to Pharo (was developped on the VisualWorks compiler) and I didn't manage to port it easily on the Pharo smalltalk compiler. I met J-C. Arnaud in Rennes yesterday and he told me I should try the Opal compiler. So, how do I load Opal in a Pharo 1.4 image ? Thanks, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 21, 2012

Re: [Pharo-project] [update 2.0] #20145

by Pavel Krivanek

The message removeAllButPackages: processes methods in classes only by categories (it uses standard message removeCategory:). So it should be fixed in the system. -- Pavel On Thu, Jun 21, 2012 at 12:44 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > I mean, privShrinkingProcess should remove the trait methods first, and then > the class methods if you do not want to rely on compiler maybe...Â Another > posibility is to copy the method, but that way they will share the same > space into the sources file maybe? I don't know that part of the system.. > > > On Thu, Jun 21, 2012 at 12:41 PM, Guillermo Polito > <guillermopolito(a)gmail.com> wrote: >> >> I think it is a bug in privShrinkingProcess that may be removing methods >> from a class, keeping the one in the trait.Â That means that when you remove >> a method from the class, the system will take the method in the trait and >> try to compile it again for the class. >> >> >> On Thu, Jun 21, 2012 at 12:33 PM, Pavel Krivanek >> <pavel.krivanek(a)gmail.com> wrote: >>> >>> http://code.google.com/p/pharo/issues/detail?id=6110 >>> >>> On Thu, Jun 21, 2012 at 12:20 PM, Guillermo Polito >>> <guillermopolito(a)gmail.com> wrote: >>> > Can you open an issue? :)Â I'll try to have a look at it tonight.Â The >>> > stack >>> > trace will make it easy :P >>> > >>> > >>> > On Thu, Jun 21, 2012 at 12:14 PM, Pavel Krivanek >>> > <pavel.krivanek(a)gmail.com> >>> > wrote: >>> >> >>> >> On Thu, Jun 21, 2012 at 11:56 AM, Mariano Martinez Peck >>> >> <marianopeck(a)gmail.com> wrote: >>> >> > >>> >> > >>> >> > On Thu, Jun 21, 2012 at 11:35 AM, Guillermo Polito >>> >> > <guillermopolito(a)gmail.com> wrote: >>> >> >> >>> >> >> PAvel, the kernel does not need any of the three actually.Â Why you >>> >> >> need >>> >> >> text in the kernel? >>> >> >> >>> >> > >>> >> > Because of TextContants. The users are: >>> >> > >>> >> > Smalltalk allClasses select: [:each | each poolDictionaryNames >>> >> > includes: >>> >> > 'TextConstants' ]Â ->Â an OrderedCollection(CharacterBlock >>> >> > CharacterScanner >>> >> > CompositionScanner EncryptedMultiDisplayScanner FontSet >>> >> > LogicalFontManager >>> >> > MetacelloScriptLoader MultiCharacterBlockScanner >>> >> > MultiCharacterScanner >>> >> > MultiDisplayScanner ParseNode ScriptLoader StandardFonts StrikeFont >>> >> > StrikeFontSet TTCFont TTCFontDescription TTCFontSet >>> >> > TTFontDescription >>> >> > TTFontReader Text TextAlignment TextLine TextStyle >>> >> > UpdatingStringMorph) >>> >> > >>> >> > so we thought the problem is Compiler. But we don't want that >>> >> > package in >>> >> > the >>> >> > kernel either ;) >>> >> > So...I removed 'Compiler' and 'Text' from #kernelPackageNames. >>> >> > The problem is now that during the shrinking we are removing >>> >> > Compiler, >>> >> > but >>> >> > we need it after ;) >>> >> >>> >> I would move out TextConstants from this package (maybe to to a >>> >> separate one) and moreover split this pool to two. DefaultFontFamily >>> >> and so on should not be needed for Compiler :-) >>> >> >>> >> > >>> >> > PharoKernel shrinking report >>> >> > Error: >>> >> > MessageNotUnderstood: CompiledMethod>>parserClass >>> >> > 341 2 BlockClosure>>cull: >>> >> > 3 BlockClosure>>cull:cull: >>> >> > 4 5 BlockClosure>>cull: >>> >> > 6 7 BlockClosure>>ensure: >>> >> > 8 MethodContext(ContextPart)>>handleSignal: >>> >> > 9 MessageNotUnderstood(Exception)>>signal >>> >> > 10 CompiledMethod(Object)>>doesNotUnderstand: #parserClass >>> >> > 11 CompiledMethod>>getSourceReplacingSelectorWith: >>> >> > 12 ClassDescription class(Behavior)>>addTraitSelector:withMethod: >>> >> > 13 14 OrderedCollection>>do: >>> >> > 15 ClassDescription class(Behavior)>>updateMethodDictionarySelector: >>> >> > 16 17 Array(SequenceableCollection)>>do: >>> >> > 18 ClassDescription class(Behavior)>>noteChangedSelectors: >>> >> > 19 ClassDescription class(Behavior)>>removeSelector: >>> >> > 20 ClassDescription class(ClassDescription)>>removeSelector: >>> >> > 21 22 Array(SequenceableCollection)>>do: >>> >> > 23 ClassDescription class(ClassDescription)>>removeCategory: >>> >> > 24 25 OrderedCollection>>do: >>> >> > 26 27 Set>>do: >>> >> > 28 SystemNavigation>>removeAllButPackages: >>> >> > 29 30 BlockClosure>>on:do: >>> >> > 31 BlockClosure>>ifError: >>> >> > 32 SmalltalkImage>>privShrinkingProcess >>> >> > 33 34 >>> >> > >>> >> > >>> >> > So I think SystemNavigation default removeAllButPackages: self >>> >> > kernelPackageNames. >>> >> > should not remove Compiler and we should do it at the end of the >>> >> > process? >>> >> > >>> >> > Pavel? >>> >> > >>> >> >>> >> Can some Traits guru explain me why we need Compiler for removing of >>> >> methods? :-) >>> >> >>> >> -- Pavel >>> >> >>> >> >> >>> >> >> On Thu, Jun 21, 2012 at 8:38 AM, Pavel Krivanek >>> >> >> <pavel.krivanek(a)gmail.com> >>> >> >> wrote: >>> >> >>> >>> >> >>> This update significantly breaks the PharoKernel generation >>> >> >>> because >>> >> >>> classes in categories Text-Edition and Text-Scanning categories >>> >> >>> cannot >>> >> >>> be in this image. >>> >> >>> >>> >> >>> Please reject and rollback this update. We need to split the >>> >> >>> package >>> >> >>> into three (Text-Core, Text-Edition, Text-Scanning) and check >>> >> >>> extension methods ownership. We need working PharoKernel for work >>> >> >>> on >>> >> >>> related jobs. >>> >> >>> >>> >> >>> Cheers, >>> >> >>> -- Pavel >>> >> >>> >>> >> >>> On Wed, Jun 20, 2012 at 6:21 PM, Esteban Lorenzano >>> >> >>> <estebanlm(a)gmail.com> >>> >> >>> wrote: >>> >> >>> > 20145 >>> >> >>> > ----- >>> >> >>> > >>> >> >>> > Issue 5945: Â Â Nice packaging for Text stuff >>> >> >>> > Â Â Â Â http://code.google.com/p/pharo/issues/detail?can=2&q=5945 >>> >> >>> > >>> >> >>> >>> >> >> >>> >> > >>> >> > >>> >> > >>> >> > -- >>> >> > Mariano >>> >> > http://marianopeck.wordpress.com >>> >> > >>> >> >>> > >>> >> >

June 21, 2012

[Pharo-project] [update 2.0] #20148

by Esteban Lorenzano

20148 ----- Issue 6097: Bad source and changes path for one click on Windows (Jenkins?) http://code.google.com/p/pharo/issues/detail?id=6097

June 21, 2012