August 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pillar] How do I open the Pillar editor in Pharo 6?

by Stephane Ducasse

I did not know it :) so this is cool. Today we improved the makefile logic and I'm about to finish a hack to give the possibility to the makefile to be fully generic. After I will finally look at Luc makefile generator because we want to move more logic to Pharo. Stef On Tue, Aug 29, 2017 at 2:20 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > On 8/28/17, Norbert Hartl <norbert(a)hartl.name> wrote: >> >>> Am 26.08.2017 um 12:56 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> In an image having Pillar, inspect a Pillar file. Something like this: >>> >>> âpath/to/file.pillar' asFileReference >>> >> I downloaded a 6.1 image, loaded pillar from catalog and inspected >> >> 'foo.pillar' asFileReference >> >> and I get >> > > The same result here. > >> >> Looks like there are additional steps needed. >> >> Norbert >> > > > If I do > > > PRPillarParser parse: > 'myExample.pillar' asFileReference contents > > > I get a nice display of the Pillar Document Object Model and the > results after using different exporter objects (HTML, DeckJS, > Markdown, AsciiDoc, Beamer, LaTeX) > > But no Pillar editor. > > --Hannes

Aug. 29, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Yves Lenfant

Thanks for your quick reply. OK, your chapter highligths the polymorpism not the inheritance. So I will try to change the Number methods in a dedicated image... Anyway, in the book InsideSmalltalk P. 250, it explains that (I quote) I suppose the "Number" mecanism is more complex than I can expect. Yves -- View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 29, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Stephane Ducasse

Yes I know this article. For the book I was trying to get an example that I can just add as an extension of a previous exercise. And I like it. On Tue, Aug 29, 2017 at 9:33 PM, Yves Lenfant <lenfantyv(a)wanadoo.fr> wrote: > I start understanding better, I found this topic in the SmalltalkWithStyle > book p. 107 > This technic was explained by Dan Ingalls in > [Ingalls 86] Ingalls, D. A Simple Technique for Handling Multiple > Polymorphism. > 347-349, Proceedings of OOPSLA '86, Portland, Or., ACM SIGPLAN 21(11). > 1986 > That you can find here: > https://pdfs.semanticscholar.org/4924/ecc75d2a30120a088740c53594065cae67ee.… > > But about the Number class I need to understand the context deeper before > understanding completely! > > Yves > > > > -- > View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 29, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Stephane Ducasse

The code of Pharo for + **may** be rewritten using double dispatch but it is not that clear to me especially the adaptToInteger logic and we do not change for the sake of it :) There are plenty of places we should improve and that are really important. In Pillar, or compiler we have many more nodes and there a Visitor is clearly the way to go. Now you should try and sketch something and let us know. There is not need to create a superclass between die and dieHandle because DD is not based on nominal subtyping. We just need objects proposing the correct API. I use abstract superclass when I want to really push on contract or interfaces. Now in this book I did not want to stress inheritance. So I wanted to have a solution stressing messages because often people forget that messages and polymorphism are powerful and not systematically linked with inheritance. Stef On Tue, Aug 29, 2017 at 6:47 PM, Yves Lenfant <lenfantyv(a)wanadoo.fr> wrote: > Ooops I wasn't int the mailing list, lets try again > > Hello Steph, > > I have questions about the concept because,probably, I miss something. > I am not sneaky, let me explain. > > If we analyse the Kernel Numbers package, and we dissect the relation > between Float, Fraction and Integer (Pharo 5.0) for example, the '+' method > in the class Integer. We read: > > + aNumber > "Refer to the comment in Number + " > > aNumber isInteger > ifTrue: [ self negative == aNumber negative > ifTrue: [ ^ (self digitAdd: aNumber) > normalize ] > ifFalse: [ ^ self digitSubtract: aNumber ] > ]. > aNumber isFraction > ifTrue: [ ^ Fraction > numerator: self * aNumber denominator + > aNumber numerator > denominator: aNumber denominator ]. > ^ aNumber adaptToInteger: self andSend: #+ > > and we have similar '+'method containing complementary tests in the other > class Float and Fraction. > And an overall '+' method in the class Number > > + aNumber > "Answer the sum of the receiver and aNumber." > > self subclassResponsibility > > > I precise that a long time ago as an academic exercice, I developped a > 'Complex' class using this way above (So I add tests). > > My questions: > You say it's better to use double dispatch, so in this case, can we apply it > for the Number subclasses? > > It is good or unnecesary to create a super class 'Dicable' containing a '+' > method with > > + aNumber > "Answer the sum of the receiver and aNumber." > > self subclassResponsibility > > ? is it wasted time or safe code? > > Yves > > > > -- > View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 29, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Yves Lenfant

I start understanding better, I found this topic in the SmalltalkWithStyle book p. 107 This technic was explained by Dan Ingalls in [Ingalls 86] Ingalls, D. A Simple Technique for Handling Multiple Polymorphism. 347-349, Proceedings of OOPSLA '86, Portland, Or., ACM SIGPLAN 21(11). 1986 That you can find here: https://pdfs.semanticscholar.org/4924/ecc75d2a30120a088740c53594065cae67ee.… But about the Number class I need to understand the context deeper before understanding completely! Yves -- View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 29, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by Stephane Ducasse

except the slides 2 and 3 of the first week :) But else all the mooc: slides, exercises were made in Pillar On Tue, Aug 29, 2017 at 3:39 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > All Pharo Mooc slides were made in pillar > > e.g. > > pillar: > https://github.com/SquareBracketAssociates/PharoMooc/blob/master/Slides/Wee… > > output: > http://rmod-pharo-mooc.lille.inria.fr/MOOC/Slides/Week3/C019-W3S03-Basic-Va… > > ( mooc.pharo.org ) > > Peter > > On Tue, Aug 29, 2017 at 2:54 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> Hello >> >> On the slide 14 of the Pillar presentation at ESUG 2015 [1] it says >> that the presentation was made with Pillar. Is the Pillar source code >> available somewhere? >> >> Other source code examples of presentations made with Pillar are fine as >> well. >> >> Thank you >> >> Hannes Hirzel >> >> >> [1] >> http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf >> >

Aug. 29, 2017

Re: [Pharo-users] [Pillar] Pillar source code of ESUG 2015 presentation? Presentations done with Pillar?

by Cyril Ferlicot D.

Le 29/08/2017 Ã 14:54, H. Hirzel a Ã©critÂ : > Hello > > On the slide 14 of the Pillar presentation at ESUG 2015 [1] it says > that the presentation was made with Pillar. Is the Pillar source code > available somewhere? > Hi! Here are the sources: https://drive.google.com/drive/folders/0B_KDRvt7h6lYbDROQ0FaXzdPeTg?usp=sha… But it was done with a version of Pillar from two years ago. I don't know if it still work perfectly. The mooc is maybe a better example since it is still building. > Other source code examples of presentations made with Pillar are fine as well. > > Thank you > > Hannes Hirzel > > > [1] http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 29, 2017

Re: [Pharo-users] CodeImporter. 256 literals limit

by Andreas Sunardi

Point well taken. Unfortunately, I'm not in charge of the infrastructure. I don't know if my experience is typical or not, but it's difficult for IT to find a period to disrupt engineering projects, potentially breaking tools, without drawing fire from engineering :) On Tue, Aug 29, 2017 at 8:45 AM, Richard Sargent < richard.sargent(a)gemtalksystems.com> wrote: > my work environment is using RedHat6/CentOS6 with glibc 2.12 >> > > That's seven years of unpatched security vulnerabilities! Are you sure you > really want to stay at such great risk? > > > On Tue, Aug 29, 2017 at 8:30 AM, Andreas Sunardi <a.sunardi(a)gmail.com> > wrote: > >> That sounds good. Unfortunately for me, my work environment is using >> RedHat6/CentOS6 with glibc 2.12. Is there Pharo6 with glibc < 2.15 support. >> Or is there a way for me to build that myself? >> >> It's quite a departure to change my DSL into defining multiple methods. >> But that's my own problem. >> >> I'm happy to hear Pharo 6 can support a lot more literals. I tested my >> code on Pharo 6 (on my Windows box) and it works. I see SistaV1 compiler in >> Pharo 5 setting, but that causes Pharo to crash. >> >> Thank you guys for your answers. I think I have the information I need to >> make decision. But if there is a way to get Pharo 6 that works with glibc < >> 2.15, please let me know. >> >> Thank you >> -- >> Andreas >> >> On Tue, Aug 29, 2017 at 12:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> If your tool works in Pharo 6, you can use the other bytecode set which >>> supports up to 32k literals. To do so, go to: >>> World Menu > Settings > Compiler > Encoder >>> and pick SistaV1 instead of V3PlusClosures >>> Try to load your code. The default Pharo 6 VM supports both bytecode >>> sets. >>> >>> Alternatively you need to split your methods with many literals in >>> multiple methods with less literals, which is usually quite tricky to do >>> right. >>> >>> On Tue, Aug 29, 2017 at 4:52 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >>> wrote: >>> >>>> I have written a tool (Pharo5) where user gives an input file to it, >>>> where the content is a smalltalk code, a DSL. I used a subclass of >>>> CodeImporter class to evaluate this input file. >>>> >>>> Recently my user used an input file where it hit the 256 literal limit >>>> (total of unique string, number, method name, etc), down in >>>> OpalEncoderForV3PlusClosures >> genPushLiteral:. The number seems to be >>>> hard coded and related to byte code generator, not something I can simply >>>> increase. I wasn't aware of this limitation. >>>> >>>> Before I overhaul my tool, I thought I should ask. Is there another >>>> alternative to evaluate a smalltalk file/script? The file is small, 27k, >>>> but the number of unique literals in it is > 256. Is it possible at all, >>>> seeing that the limit is related to byte code generator. >>>> >>>> Thank you in advance >>>> -- >>>> Andreas Sunardi >>>> >>> >>> >> >

Aug. 29, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Yves Lenfant

Ooops I wasn't int the mailing list, lets try again Hello Steph, I have questions about the concept because,probably, I miss something. I am not sneaky, let me explain. If we analyse the Kernel Numbers package, and we dissect the relation between Float, Fraction and Integer (Pharo 5.0) for example, the '+' method in the class Integer. We read: + aNumber "Refer to the comment in Number + " aNumber isInteger ifTrue: [ self negative == aNumber negative ifTrue: [ ^ (self digitAdd: aNumber) normalize ] ifFalse: [ ^ self digitSubtract: aNumber ] ]. aNumber isFraction ifTrue: [ ^ Fraction numerator: self * aNumber denominator + aNumber numerator denominator: aNumber denominator ]. ^ aNumber adaptToInteger: self andSend: #+ and we have similar '+'method containing complementary tests in the other class Float and Fraction. And an overall '+' method in the class Number + aNumber "Answer the sum of the receiver and aNumber." self subclassResponsibility I precise that a long time ago as an academic exercice, I developped a 'Complex' class using this way above (So I add tests). My questions: You say it's better to use double dispatch, so in this case, can we apply it for the Number subclasses? It is good or unnecesary to create a super class 'Dicable' containing a '+' method with + aNumber "Answer the sum of the receiver and aNumber." self subclassResponsibility ? is it wasted time or safe code? Yves -- View this message in context: http://forum.world.st/new-chapter-on-double-dispatch-for-new-book-tp4963645… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 29, 2017

Re: [Pharo-users] CodeImporter. 256 literals limit

by Richard Sargent

> > my work environment is using RedHat6/CentOS6 with glibc 2.12 > That's seven years of unpatched security vulnerabilities! Are you sure you really want to stay at such great risk? On Tue, Aug 29, 2017 at 8:30 AM, Andreas Sunardi <a.sunardi(a)gmail.com> wrote: > That sounds good. Unfortunately for me, my work environment is using > RedHat6/CentOS6 with glibc 2.12. Is there Pharo6 with glibc < 2.15 support. > Or is there a way for me to build that myself? > > It's quite a departure to change my DSL into defining multiple methods. > But that's my own problem. > > I'm happy to hear Pharo 6 can support a lot more literals. I tested my > code on Pharo 6 (on my Windows box) and it works. I see SistaV1 compiler in > Pharo 5 setting, but that causes Pharo to crash. > > Thank you guys for your answers. I think I have the information I need to > make decision. But if there is a way to get Pharo 6 that works with glibc < > 2.15, please let me know. > > Thank you > -- > Andreas > > On Tue, Aug 29, 2017 at 12:34 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >> Hi, >> >> If your tool works in Pharo 6, you can use the other bytecode set which >> supports up to 32k literals. To do so, go to: >> World Menu > Settings > Compiler > Encoder >> and pick SistaV1 instead of V3PlusClosures >> Try to load your code. The default Pharo 6 VM supports both bytecode sets. >> >> Alternatively you need to split your methods with many literals in >> multiple methods with less literals, which is usually quite tricky to do >> right. >> >> On Tue, Aug 29, 2017 at 4:52 AM, Andreas Sunardi <a.sunardi(a)gmail.com> >> wrote: >> >>> I have written a tool (Pharo5) where user gives an input file to it, >>> where the content is a smalltalk code, a DSL. I used a subclass of >>> CodeImporter class to evaluate this input file. >>> >>> Recently my user used an input file where it hit the 256 literal limit >>> (total of unique string, number, method name, etc), down in >>> OpalEncoderForV3PlusClosures >> genPushLiteral:. The number seems to be >>> hard coded and related to byte code generator, not something I can simply >>> increase. I wasn't aware of this limitation. >>> >>> Before I overhaul my tool, I thought I should ask. Is there another >>> alternative to evaluate a smalltalk file/script? The file is small, 27k, >>> but the number of unique literals in it is > 256. Is it possible at all, >>> seeing that the limit is related to byte code generator. >>> >>> Thank you in advance >>> -- >>> Andreas Sunardi >>> >> >> >

Aug. 29, 2017