- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Fuel Release Version 1.8

by StÃ©phane Ducasse

On May 28, 2012, at 7:44 PM, Jaroslaw Podgajny wrote: > Hi guys, > > It has been long time since I looked into Pharo and licensing environment (revitalising my interest now...), so I may be asking obvious questions but what is the licencing model for Fuel? (skimmed the mail and the web site and only noted "open-sourced") good point. It is MIT as the complete pharo environment. Stef > > > > Regards, Jaroslaw > > > On Sunday, May 27, 2012, Igor Stasenko wrote: > On 27 May 2012 21:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > > > > >> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at > >> #20094). Please check our documentation [2] for complete installation > >> and use guides > > > > > > > > Martin told me something by private email that I think is worth to mention. > > Not sure if you read it carefully, but Fuel is working from Pharo version > > 1.1 up to 2.0!!! > > But he is mentioned that already in his announcement. :) > This is nice, of course! > > > > One of reasons is to help people migrate to new Pharo versions by using Fuel > > as a way of moving data. > > > > Cheers > > > >> . > >> > >> Below, there are some remarkable changes. > >> > >> - Much more complete user guides. > >> - Improved API for customizing how graph is traced. > >> - FuelMetalevel: serialization of stuff like classes and compiled > >> methods moved to an optional package. > >> - Customize objects to be treated as globals. > >> - Migrations: declare at materialization time class and variables renames. > >> - Weak references properly managed. Thanks to Juan Vuletich and Levente. > >> - Thanks Pavel for helping us improving FuelPackageLoader with > >> wonderful ideas and bug reports. > >> - Serialization speed up on large graphs by using specialized > >> collections. Thanks Levente. > >> - Encoder and Decoder: new reifications that clarify the design. > >> Thanks Colin Putney. > >> - Optimized serialization of "clean" BlockClosures, which don't need > >> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. > >> - Added a clear error hierarchy. > >> - Debug facilities, including graph visualization using Roassal. > >> Thanks Alexandre and Doru. > >> - Many more new tests. Including those from extension packages, we > >> have almost 600 tests. > >> - Repository moved from 'http://www.squeaksource.com/Fuel' to > >> 'http://ss3.gemstone.com/ss/Fuel'. > >> > >> If you are a Fuel user we are not aware of, please let us know! > >> > >> Best regards, > >> Martin and Mariano > >> > >> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel > >> [2]: > >> http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation > >> > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Best regards, > Igor Stasenko. >

May 28, 2012

Re: [Pharo-project] [ANN] Fuel Release Version 1.8

by Francois Stephany

Hi, The homepage http://ss3.gemstone.com/ss/Fuel.html says that all the code commited in the repo is MIT Licence. Cheers, Francois On 28/05/12 10:44, Jaroslaw Podgajny wrote: > Hi guys, > > It has been long time since I looked into Pharo and licensing > environment (revitalising my interest now...), so I may be asking > obvious questions but what is the licencing model for Fuel? (skimmed > the mail and the web site and only noted "open-sourced") > > > > Regards, Jaroslaw > > > On Sunday, May 27, 2012, Igor Stasenko wrote: > > On 27 May 2012 21:23, Mariano Martinez Peck <marianopeck(a)gmail.com > <javascript:;>> wrote: > > > > > > > >> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at > >> #20094). Please check our documentation [2] for complete > installation > >> and use guides > > > > > > > > Martin told me something by private email that I think is worth > to mention. > > Not sure if you read it carefully, but Fuel is working from Pharo > version > > 1.1 up to 2.0!!! > > But he is mentioned that already in his announcement. :) > This is nice, of course! > > > > One of reasons is to help people migrate to new Pharo versions by > using Fuel > > as a way of moving data. > > > > Cheers > > > >> . > >> > >> Below, there are some remarkable changes. > >> > >> - Much more complete user guides. > >> - Improved API for customizing how graph is traced. > >> - FuelMetalevel: serialization of stuff like classes and compiled > >> methods moved to an optional package. > >> - Customize objects to be treated as globals. > >> - Migrations: declare at materialization time class and > variables renames. > >> - Weak references properly managed. Thanks to Juan Vuletich and > Levente. > >> - Thanks Pavel for helping us improving FuelPackageLoader with > >> wonderful ideas and bug reports. > >> - Serialization speed up on large graphs by using specialized > >> collections. Thanks Levente. > >> - Encoder and Decoder: new reifications that clarify the design. > >> Thanks Colin Putney. > >> - Optimized serialization of "clean" BlockClosures, which don't need > >> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. > >> - Added a clear error hierarchy. > >> - Debug facilities, including graph visualization using Roassal. > >> Thanks Alexandre and Doru. > >> - Many more new tests. Including those from extension packages, we > >> have almost 600 tests. > >> - Repository moved from 'http://www.squeaksource.com/Fuel' to > >> 'http://ss3.gemstone.com/ss/Fuel'. > >> > >> If you are a Fuel user we are not aware of, please let us know! > >> > >> Best regards, > >> Martin and Mariano > >> > >> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel > >> [2]: > >> > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation > >> > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Best regards, > Igor Stasenko. > -- http://tulipemoutarde.be CA: +1 778 558 3225 BE: +32 65 709 131

May 28, 2012

Re: [Pharo-project] [ANN] Fuel Release Version 1.8

by Jaroslaw Podgajny

Hi guys, It has been long time since I looked into Pharo and licensing environment (revitalising my interest now...), so I may be asking obvious questions but what is the licencing model for Fuel? (skimmed the mail and the web site and only noted "open-sourced") Regards, Jaroslaw On Sunday, May 27, 2012, Igor Stasenko wrote: > On 27 May 2012 21:23, Mariano Martinez Peck <marianopeck(a)gmail.com<javascript:;>> > wrote: > > > > > > > >> Fuel works out of the box in Pharo from 1.1 up to 2.0 (checked at > >> #20094). Please check our documentation [2] for complete installation > >> and use guides > > > > > > > > Martin told me something by private email that I think is worth to > mention. > > Not sure if you read it carefully, but Fuel is working from Pharo version > > 1.1 up to 2.0!!! > > But he is mentioned that already in his announcement. :) > This is nice, of course! > > > > One of reasons is to help people migrate to new Pharo versions by using > Fuel > > as a way of moving data. > > > > Cheers > > > >> . > >> > >> Below, there are some remarkable changes. > >> > >> - Much more complete user guides. > >> - Improved API for customizing how graph is traced. > >> - FuelMetalevel: serialization of stuff like classes and compiled > >> methods moved to an optional package. > >> - Customize objects to be treated as globals. > >> - Migrations: declare at materialization time class and variables > renames. > >> - Weak references properly managed. Thanks to Juan Vuletich and Levente. > >> - Thanks Pavel for helping us improving FuelPackageLoader with > >> wonderful ideas and bug reports. > >> - Serialization speed up on large graphs by using specialized > >> collections. Thanks Levente. > >> - Encoder and Decoder: new reifications that clarify the design. > >> Thanks Colin Putney. > >> - Optimized serialization of "clean" BlockClosures, which don't need > >> the whole stack of contexts. Thanks Juan Vuletich and Eliot Miranda. > >> - Added a clear error hierarchy. > >> - Debug facilities, including graph visualization using Roassal. > >> Thanks Alexandre and Doru. > >> - Many more new tests. Including those from extension packages, we > >> have almost 600 tests. > >> - Repository moved from 'http://www.squeaksource.com/Fuel' to > >> 'http://ss3.gemstone.com/ss/Fuel'. > >> > >> If you are a Fuel user we are not aware of, please let us know! > >> > >> Best regards, > >> Martin and Mariano > >> > >> [1]: http://rmod.lille.inria.fr/web/pier/software/Fuel > >> [2]: > >> > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation > >> > > > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Best regards, > Igor Stasenko. > >

May 28, 2012

Re: [Pharo-project] Refactoring Questions

by Davide Varvello

Hi there, Any news about that improvement? I seconded Camillo. Cheers Davide -- View this message in context: http://forum.world.st/Refactoring-Questions-tp4394983p4632209.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 28, 2012

Re: [Pharo-project] class message

by Igor Stasenko

On 28 May 2012 15:30, Ben Coman <btc(a)openinworld.com> wrote: > Mariano Martinez Peck wrote: >>>>>>> >>>>>>> So questions: >>>>>>> Is ProtoObject should implement #class? >>>>>>> Can we move #class method from Object to ProtoObject? >>>>>>> >>>>>>> >>>>>> >>>>>> ups....good catch! indeed, we should move it to ProtoObject. >>>>>> >>>>>> >>>>> >>>>> mm.. why? >>>>> >>>> >>>> Because ALL objects do have a class. Right? if you want to change the >>>> semantics of #class then just subclass and change it. >>>> >>> >>> mmm.. no. >>> IMO, in pure sense, all objects having behavior. but behavior is not a >>> class (and we can even have >>> two classes to discriminate between them). >>> yes, it is _almost_ a class.. but much more obscure.. i doesn't needs to >>> be compatible with Class protocol.. You should know pretty well, what >>> requirements VM side puts >>> for a valid behavior: - superclass, methoddict, format. >>> which enables VM to do method lookup and creating an instances. >>> >>> now, if you make ProtoObject to answer message #class, one will assume >>> that >>> the object it answers should conform to a full-fledged Class protocol. >>> But of course it should not. >>> >>> Maybe i nitpicking about terminology.. but i think at that level we >>> should make it clear: >>> - all objects having behavior! >>> > > > A passing naive thought... > Does ProtoObject then need #behavior? Â ...which can be overridden to return > Class, Metaclass or Other as appropriate? ...such that Mocketry, > #cannotInterpret and #pointsTo etc can use this instead of #class? > i dont have a strong opinion. from one side it is good to have a separate method for that, just to indicate that protoobject don't needs to have a fully formed class. from another side, its implementation will be same as in #class, and #behavior selector may be used already by various projects for different purposes. > >>> - some object's behaviors are Classes >>> - some object's behaviors are Metaclasses >>> - but there could be any other. >>> >>> >>> >> >> I agree with all that. But as you said, I think you are going too low >> level >> in details. >> For example, I would call class to all your previous list. All objects >> have >> a class, which can be Class, Metaclass, whatever. >> In addition, if we don't add #class in ProtoObject, then there are some of >> broken messages like #cannotInterpret: and #pointsTo since they send >> #class >> to self. >> >> >> > > > > > -- Best regards, Igor Stasenko.

May 28, 2012

Re: [Pharo-project] [ANN] NativeBoost 1.2 version released (#development)

by Luc Fabresse

Hi all, Thanks Igor! Excellent and fast job ;-) I will test this new version soon. #Luc 2012/5/28 Lawson English <lenglish5(a)cox.net> > On 5/28/12 12:14 AM, Igor Stasenko wrote: > >> Hi, there >> >> i prepared new Metacello configuration of NativeBoost. >> >> Here the list of changes: >> >> >> > Sounds good. I will modify my test of gmp bindings to use it. > > BTW, for anyone interested, here is a way of creating "batch" bindings to > the gmplib big integer add call: > > > http://pastebin.com/naj05wEe > > makes two successive calls to the same (could be a different) function > from within the same method. This avoids the overhead of the marshaling of > parameters and making successive calls via the VM. With this technique, you > could perform a reasonably complex task in an external lib with a single > method. Extra assembler code can be placed in the same block, for extra > speedy goodness. > > Now, in order to keep the Squeak Wayâ¢, we need a way of writing the code > in slang instead of assembler. > > > L > > > -- > Squeak from the very start (introduction to Squeak and Pharo Smalltalk for > the (almost) complete and compleate beginner). > https://www.youtube.com/**playlist?list=**PL6601A198DF14788D&feature=** > view_all<https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all> > > >

May 28, 2012

Re: [Pharo-project] [ANN] NativeBoost 1.2 version released (#development)

by Igor Stasenko

On 28 May 2012 10:17, Lawson English <lenglish5(a)cox.net> wrote: > On 5/28/12 12:14 AM, Igor Stasenko wrote: >> >> Hi, there >> >> i prepared new Metacello configuration of NativeBoost. >> >> Here the list of changes: >> >> > > Sounds good. I will modify my test of gmp bindings to use it. > > BTW, for anyone interested, here is a way of creating "batch" bindings to > the gmplib Â big integer add call: > > > http://pastebin.com/naj05wEe > > makes two successive calls to the same (could be a different) function from > within the same method. This avoids the overhead of the marshaling of > parameters and making successive calls via the VM. With this technique, you > could perform a reasonably complex task in an external lib with a single > method. Extra assembler code can be placed in the same block, for extra > speedy goodness. > > Now, in order to keep the Squeak Wayâ¢, we need a way of writing the code in > slang instead of assembler. > Yes. I also want to use some kind of assembler DSL, instead of hardcoding the platform-specific instructions everywhere. Of course , i want to make it flexible, so if you still need to invoke platform-specific instruction, you should be able to do that. -- Best regards, Igor Stasenko.

May 28, 2012

Re: [Pharo-project] class message

by Ben Coman

Mariano Martinez Peck wrote: >>>>>> So questions: >>>>>> Is ProtoObject should implement #class? >>>>>> Can we move #class method from Object to ProtoObject? >>>>>> >>>>>> >>>>> ups....good catch! indeed, we should move it to ProtoObject. >>>>> >>>>> >>>> mm.. why? >>>> >>> Because ALL objects do have a class. Right? if you want to change the >>> semantics of #class then just subclass and change it. >>> >> mmm.. no. >> IMO, in pure sense, all objects having behavior. but behavior is not a >> class (and we can even have >> two classes to discriminate between them). >> yes, it is _almost_ a class.. but much more obscure.. i doesn't needs to >> be compatible with Class protocol.. You should know pretty well, what >> requirements VM side puts >> for a valid behavior: - superclass, methoddict, format. >> which enables VM to do method lookup and creating an instances. >> >> now, if you make ProtoObject to answer message #class, one will assume that >> the object it answers should conform to a full-fledged Class protocol. >> But of course it should not. >> >> Maybe i nitpicking about terminology.. but i think at that level we >> should make it clear: >> - all objects having behavior! >> A passing naive thought... Does ProtoObject then need #behavior? ...which can be overridden to return Class, Metaclass or Other as appropriate? ...such that Mocketry, #cannotInterpret and #pointsTo etc can use this instead of #class? >> - some object's behaviors are Classes >> - some object's behaviors are Metaclasses >> - but there could be any other. >> >> >> > I agree with all that. But as you said, I think you are going too low level > in details. > For example, I would call class to all your previous list. All objects have > a class, which can be Class, Metaclass, whatever. > In addition, if we don't add #class in ProtoObject, then there are some of > broken messages like #cannotInterpret: and #pointsTo since they send #class > to self. > > >

May 28, 2012

Re: [Pharo-project] thanks for pharoconf

by Usman Bhatti

On Mon, May 28, 2012 at 11:03 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > Usman, > > Update done, including link to your Inria page. > Now its much better :-). Thanx Usman > > KR > Phil > > 2012/5/27 Usman Bhatti <usman.bhatti(a)gmail.com> > >> >> >> On Sun, May 27, 2012 at 12:58 PM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: >> >>> Yes, very interesting, motivating, and results producing! >>> >>> Thanks a ton for making it a reality. >>> >>> Two blog posts of mine just in case you are interested: >>> >>> http://philippeback.be/2012/05/first-day-of-pharoconf-in-lille/ >>> http://philippeback.be/2012/05/second-day-at-pharoconf-in-lille/ >>> >> >> Thanx for the post, Phil. It was nice talking to you and other people at >> Pharo conf. Igor rightly mentioned that the conference was a moral booster >> for all of us... >> >> Now back to work. >> >> Usman Bhatti >> (I hope you dont forget my name anymore :-) >> >> >>> >>> Thanks again! >>> >>> Philippe Back >>> >>> 2012/5/27 Norbert Hartl <norbert(a)hartl.name> >>> >>>> Yes, >>>> >>>> was fun to see a lot of you. And I could add some new faces to my >>>> inventory. Great! >>>> >>>> Norbert >>>> >>>> Am 27.05.2012 um 00:12 schrieb Tudor Girba: >>>> >>>> > Hi, >>>> > >>>> > I had a good time at PharoConf. >>>> > >>>> > Thanks for organizing it. >>>> > >>>> > Cheers, >>>> > Doru >>>> > >>>> > >>>> > -- >>>> > www.tudorgirba.com >>>> > >>>> > "Beauty is where we see it." >>>> > >>>> > >>>> > >>>> > >>>> >>>> >>>> >>> >>> >>> -- >>> Philippe Back >>> "Helping you hit the top 3 outcomes you really want to achieve" >>> >>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: >>> phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >>> http://philippeback.be >>> >>> High Octane SPRL >>> rue cour Boisacq 101 >>> 1301 Bierges >>> >>> >> > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: > http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > >

May 28, 2012

[Pharo-project] Tests Guard page

by Pavel Krivanek

Hi, to start to make some progress in Pharo 2.0 failing tests processing, I started this page: http://code.google.com/p/pharo/wiki/TestsGuard Please feel free to update end extend it. Cheers, -- Pavel

May 28, 2012