- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Please help us by buying the book

by Esteban A. Maringolo

2013/9/19 kilon <thekilon(a)yahoo.co.uk>: > Just ordered the book in Lulu. Please don't spend all my money on beer :D Why not? they deserve it! :) Esteban

Sept. 20, 2013

Re: [Pharo-dev] bytecode table

by Camillo Bruni

cool, I'll keep a local copy of that ;) On 2013-09-19, at 10:01, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Hey, > > Yesterday I printed the bytecode set of Pharo / Squeak (named > SqueakV3PlusClosure) in a nice way to have a better overview. > > Perhaps some people will be interested in it. You can print it on a A3. > > Best, > > PS: Thanks Guille for the page layout, margins and stuff. > <ByteCode.pdf>

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by GOUBIER Thierry

Ok, I've added issue 11639 for the backport. I'll make a try tonight. Thierry ________________________________________ De : Pharo-dev [pharo-dev-bounces(a)lists.pharo.org] de la part de Esteban Lorenzano [estebanlm(a)gmail.com] Date d'envoi : jeudi 19 septembre 2013 17:33 Ã : Pharo Development List Objet : Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3 is a really annoying combination of problems: 1) the abuse of on:do: for register announcers, usually in SystemAnnouncer singleton, who then register immortal announcements. 2) the abuse of weak message in places where is not needed (like in non global announcements who then will be collected when owner collected) 3) a weird case when instead a WeakAnnouncementSubscription, system was registering LegacyWeakSubscription, and this one uses WeakRegistry (which is a singleton too)... so, if combined with #on:do:, the subscriptions were becoming immortal too. So far, we think that is all the problem. You need two steps (the 3rd was because I forgot to commit something :p) because after changing somethign in the finalization process, you then need to restart it to be able to remove old/not used methods. cheers, Esteban On Sep 19, 2013, at 5:30 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 19/09/2013 17:20, Esteban Lorenzano a Ã©crit : >> Hi, >> >> I just submitted and integrated a fix for the leak problem. >> That should fix the problem we are having in Pharo3... now we need to work on a backport for Pharo2... any takers? :) > > I need some explanations :) > > Thierry > >> Esteban >> >> > > -- > 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 >

Sept. 19, 2013

Re: [Pharo-dev] Please help us by buying the book

by kilon

Just ordered the book in Lulu. Please don't spend all my money on beer :D kilon wrote > > Damien Cassou wrote >> On Tue, Sep 17, 2013 at 12:22 AM, kilon < >> thekilon@.co >> > wrote: >>> how long for the amazon version ? I am Greek and I am not sure if the >>> first >>> choice delivers here. >> >> >> the amazon version is there: http://deepintopharo.com/. >> >> Still, we get more money if you go through lulu. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill > fair enough I will get it through lulu, I already have the pdf version > anyway so its not that I can't wait. -- View this message in context: http://forum.world.st/Please-help-us-by-buying-the-book-tp4708575p4709232.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 19, 2013

Re: [Pharo-dev] [Seaside] Re: Grease conflicts #packages with RPackage

by Mariano Martinez Peck

On Mon, Sep 9, 2013 at 6:01 AM, Philippe Marschall < philippe.marschall(a)gmail.com> wrote: > On Fri, Sep 6, 2013 at 3:21 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > Anyone? > > use anRPackageOrganizer, or better delegate to anRPackageOrganizer > > I didn't understand your answer. Could you explain more please? I keep having this problem each time I build an image in Pharo 2.0.... I would like to at least simply rename GRPackage class #packages to #greasePackages. Can I proceed and commit? > Cheers > Philippe > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Mariano http://marianopeck.wordpress.com

Sept. 19, 2013

Re: [Pharo-dev] [Pharo-users] Fwd: PhaROS - VirtualBox.

by Luc Fabresse

Thanks Santiago. And we want screenshots and videos too ;-) Luc 2013/9/19 Santiago Bragagnolo <santiagobragagnolo(a)gmail.com> > > > Hi all! For people that went ESUG probaby this is already known, but, in > Ecole des mines de Douai we are working in PhaROS, which is a client > framework for ROS operative system. > > So, if you are interested in get a bit into or deeper, here is a link. > > > http://car.mines-douai.fr/2013/09/pharos-virtualbox-image/ > > > > There you can find an explaining post and a link to a virtualbox image > with everything installed :). > > > We will have an issue tracker soon, meanwhile, if you use it and you have > blames or issues, send me email with [PhaROS] in the subject please! > > Thank you very much, i hope you enjoy it :). > > > Santiago. > > > > > > >

Sept. 19, 2013

Talkffi problems when generating structs with function pointers

by Rocio Amaya

Hi! i found a problem while playing with TalkFFI generation of MySQL( yes, thats probably not the path we are going to take but i am doing init to learn). The generation throws a problem with the following struct. typedef struct my_collation_handler_st { my_bool (*init)(struct charset_info_st *, void *(*alloc)(size_t)); /* Collation routines */ int (*strnncoll)(struct charset_info_st *, const uchar *, size_t, const uchar *, size_t, my_bool); int (*strnncollsp)(struct charset_info_st *, const uchar *, size_t, const uchar *, size_t, my_bool); size_t (*strnxfrm)(struct charset_info_st *c, uchar *a, size_t g, const uchar *b, size_t h); size_t (*strnxfrmlen)(struct charset_info_st * aa, size_t bb); my_bool (*like_range)(struct charset_info_st *, const char *s, size_t s_length, pchar w_prefix, pchar w_one, pchar w_many, size_t res_length, char *min_str, char *max_str, size_t *min_len, size_t *max_len); int (*wildcmp)(struct charset_info_st *, const char *str,const char *str_end, const char *wildstr,const char *wildend, int escape,int w_one, int w_many); int (*strcasecmp)(struct charset_info_st *, const char *, const char *); uint (*instr)(struct charset_info_st *, const char *b, size_t b_length, const char *s, size_t s_length, my_match_t *match, uint nmatch); /* Hash calculation */ void (*hash_sort)(struct charset_info_st *cs, const uchar *key, size_t len, ulong *nr1, ulong *nr2); my_bool (*propagate)(struct charset_info_st *cs, const uchar *str, size_t len); } MY_COLLATION_HANDLER; As you can see the struct has eleven fields which are functions pointers. However, when we generate with TalkFFI it s fails, and we can see that the struct generate is the following: an OrderedCollection( #MySQLMySysH25Cb->'init' #MySQLMySysH26Cb->'strnncoll' #MySQLMySysH26Cb->'strnncollsp' {#NBInt32. {'NBInt32 *'->'arg1'}}->'size_t' #MySQLMySysH27Cb->'like_range' #MySQLMySysH28Cb->'wildcmp' #MySQLMySysH6Cb->'strcasecmp' #MySQLMySysH29Cb->'instr' #MySQLMySysH30Cb->'hash_sort' #MySQLMySysH31Cb->'propagate' ) The generate struct have only ten fields and the fourth is wrongly generated. Instead of the two fields strnxfrm and strnxfrmlen , it generates garbage. We were with guille debugging and playing with the struct declaration with not much results. Thanks for any help rochi and guille.

Sept. 19, 2013

Re: [Pharo-dev] Forking

by Max Leske

I have a little experience. But if you want the guru you should contact Dave Lewis. He's the author of OSProcess and has written the forking code: http://wiki.squeak.org/squeak/708. But maybe I can help to answer some of your questions. What exactly do you need to know (hint: forking with the PharoVM, i.e. NativeBoost, doesn't work properly yet)? Cheers, Max On 19.09.2013, at 19:23, Guido Chari <charig(a)gmail.com> wrote: > Does anyone have experience on doing native forks from an image? > > We would like to do them for trying to experiment with an image-side native debugger and we want to know if someone know the restrictions the vm imposed for doing the fork. > > Cheers

Sept. 19, 2013

Re: [Pharo-dev] [SOLVED]ConfigurationOfGlorpDBX for Pharo2.0

by Mariano Martinez Peck

On Thu, Sep 19, 2013 at 2:22 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > > On Thu, Sep 19, 2013 at 5:16 AM, Federico.Balaguer < > federico.balaguer(a)gmail.com> wrote: > >> It actually worked, the image was unresponsive for a couple minutes but >> after >> that everything (so far) seems to be working. >> > > That is probably because of something in the progress bar only:). And yes, > loading glorp in generally takes some time. > > >> >> Thanks again! Federico >> > > Thanks to you! Can you keep us updated if you have any problem? At some > point I should update the configuration :). > > Mariano, you are using glorp in 20 also, aren't you? > > Yes, but not that much and so far with the native Postgres driver ;) But no problem so far. > >> >> >> -- >> View this message in context: >> http://forum.world.st/ConfigurationOfGlorpDBX-for-Pharo2-0-tp4709086p470909… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > -- Mariano http://marianopeck.wordpress.com

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by StÃ©phane Ducasse

> Good news... > > I saw that Seaside 3.x was okay with Pharo 3. > > I am starting a new project. Should I start with Pharo3 right away? We are trying not to break code but it can happen. So you can be always a bit behind cutting edge. Stef > is a really annoying combination of problems: > > 1) the abuse of on:do: for register announcers, usually in SystemAnnouncer singleton, who then register immortal announcements. > 2) the abuse of weak message in places where is not needed (like in non global announcements who then will be collected when owner collected) > 3) a weird case when instead a WeakAnnouncementSubscription, system was registering LegacyWeakSubscription, and this one uses WeakRegistry (which is a singleton too)... so, if combined with #on:do:, the subscriptions were becoming immortal too. > > So far, we think that is all the problem. > > You need two steps (the 3rd was because I forgot to commit something :p) because after changing somethign in the finalization process, you then need to restart it to be able to remove old/not used methods. > > cheers, > Esteban > > On Sep 19, 2013, at 5:30 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > > > > > Le 19/09/2013 17:20, Esteban Lorenzano a Ã©crit : > >> Hi, > >> > >> I just submitted and integrated a fix for the leak problem. > >> That should fix the problem we are having in Pharo3... now we need to work on a backport for Pharo2... any takers? :) > > > > I need some explanations :) > > > > Thierry > > > >> Esteban > >> > >> > > > > -- > > 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 > > > > >

Sept. 19, 2013