- Pharo-users - lists.pharo.org

Traits score: Squeak: 1, Pharo5: 0

by Hilaire

So it looks like Squeak[1] is capable to produce a correct .mcz file, out of a package coming with Traits and class. By correct, read the Traits logic is not lost. Hilaire [1] I tested with a Squeak6 alpha waiting somewhere on my disk -- Dr. Geo http://drgeo.eu

April 14, 2017

[ANN] Prometheas : a Pharo wiki database

by Dimitris Chloupis

Part of my Discord bot as a goal was to add the ability to create database entries so that people can quickly find documentation. It was quite a challenge for me because I had to learn how heroku works, PostgreSQL and all the other things but I did it!!! In any discord channel you have now 3 commands !doc , !docadd , !docremove 1) !doc <search_term> search for a term in the documentation database eg. !doc pharo 2) !docadd <search_term> <content> <tags> <links> add a new entry to the documentation database eg. !docadd "pharo" "Pharo is a modern implementation of Smalltalk" "{'smalltalk','live coding','language'}" "{'squeak','IDE'}" 3)!docremove <search_term> remove a term from database eg. !docremove pharo tags , is for more complex searches in the future, links for sending users to relevant documentation I am also planning to give access to pharo users to the database from inside the pharo image, if its easy enough to use PostgreSQL from inside Pharo. Currently the bot is fully coded in python. The goal is not to create a full documentation but rather quick help tips for fast pointing to the right direction. This is also an invite to experience pharo devs and newcomers to start adding to this database. The database is PostgreSQL , one of the most populars, I have nothing against MongoDB , its just that it works better with heroku where I host the database. But if in the future find a way to do it for free I can move to MongoDB, but no promises. Anyway this was an excuse for me to learn database programming that I had abandoned 25 years ago (DBASE). So have fun with this :)

April 14, 2017

Re: [Pharo-users] Traits, method flatten

by Hilaire

Ah, no my bad. Squeak was file in correctly the Trait and Class, it is just that its browser does not let you know if a method class belong to one of its Traits or the class itself Le 14/04/2017 Ã 11:16, Hilaire a Ã©crit : > Give a try to filein the correct .st source file of the Traits+Classes > package. It does not get it right :( > > Pharo5 get it right when loading the .st source file though. > > Still investigating... -- Dr. Geo http://drgeo.eu

April 14, 2017

Re: [Pharo-users] How can I set the SmaccDebugParser in Moose

by Stephane Ducasse

Andrei? Help? On Fri, Apr 7, 2017 at 3:14 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > I found the SmaCCParserDebugger and I found the debug menu in the Smacc > tool. > Now I get a GT and byteCode debugger but I do not find a way to make the > new debugger actif. > > Stef >

April 14, 2017

Re: [Pharo-users] why is adding instance variables so slow?

by Denis Kudriashov

2017-04-14 11:09 GMT+02:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > Hi, I think the problem was not clearly explained. This is the scenario > that is problematic. > This scenario does not happen in the new Spur implementation of > forwarding, but I think is happening in the old one. > > 1. You have, let's say 3 instances of ClassA. > 2. You add a new instance variable to ClassA. It produces > 2a. A new ClassAv2 is created with the instances variables of ClassA > and the newone > 2b. 3 Instances of ClassAv2 are created > 2c. The values of the instance variables of ClassA are copied to the > ones in ClassAv2 (the ones missing are left in nil). > 2d. The 3 instances of ClassA are becomed forward to the 3 instances of > ClassAv2 > 2e. The ClassA is becomed forward ClassAv2 > I still not see why my example not reflects all these steps. I checked also scenario with class becoming: c1 := Class1 new. c2 := Class2 new. c1 becomeForward: c2. Class1 becomeForward: Class2. Class2 allInstances "=>#(aClass2)" It also works in Cog

April 14, 2017

Re: [Pharo-users] Pharo 6 snap install

by Luke Gorrie

On 14 April 2017 at 08:53, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > We always try to have a major release around mid/end of april > Once the dust settles, I think it would be wonderful to have this invariant: - The latest Pharo VM source release is compatible with the latest Pharo image. This would make it easy for me to help nix users. My job will be to package the latest source release of the VM, period, and I will know that users can use this to run the latest image. I don't have much scope to screw things up and make people sad e.g. by shipping a bad commit from the master branch. (Of course it makes life harder for you upstream Pharo maintainers. Now updating the VM source release is a blocker for releasing a new image. Could be that this is too constraining in practice, I dunno. I'm just a guy who wants to setup a stable Pharo that I can use to build an application :-))

April 14, 2017

Re: [Pharo-users] why is adding instance variables so slow?

by Denis Kudriashov

2017-04-14 10:51 GMT+02:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > Hi Denis, > in the script you are not generating instances of Class1, the problem > is with the instances. > But it generates: c1 := Class1 new. Or what kind of generation you mean?

April 14, 2017

Re: [Pharo-users] why is adding instance variables so slow?

by Igor Stasenko

i don't see much difference comparing to old implementation of #becomeForward: the only issue is that #allInstances could report same instance twice first, it will find an old instance (that is forwards to new one) and so, add it to results array, and then walking the heap further will find a new version of same instance. That's why , it think #allInstances should use IdentitySet-behavior to mitigate such problem, and always look if there's already same object captured to avoid reporting it twice. Or else we can declare it as a feature and warn users of #allInstances that they could have duplications, so in case if it important to them, they could always do 'allInstances asIdentitySet' But again, this is soooo orthogonal to adding instance variables to class... maybe we should rename the topic instead and speak about #allInstances behavior? :) On 14 April 2017 at 12:09, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hi, I think the problem was not clearly explained. This is the scenario > that is problematic. > This scenario does not happen in the new Spur implementation of > forwarding, but I think is happening in the old one. > > 1. You have, let's say 3 instances of ClassA. > 2. You add a new instance variable to ClassA. It produces > 2a. A new ClassAv2 is created with the instances variables of ClassA > and the newone > 2b. 3 Instances of ClassAv2 are created > 2c. The values of the instance variables of ClassA are copied to the > ones in ClassAv2 (the ones missing are left in nil). > 2d. The 3 instances of ClassA are becomed forward to the 3 instances of > ClassAv2 > 2e. The ClassA is becomed forward ClassAv2 > > 3. You add a new instance variable to ClassAv2. It produces > 3a. A new ClassAv3 is created with the instances variables of ClassAv2 > and the newone > 3b. 3 Instances of ClassAv3 are created > 3c. The values of the instance variables of ClassAv2 are copied to the > ones in ClassAv3 (the ones missing are left in nil). > 3d. The 3 instances of ClassAv2 are becomed forward to the 3 instances > of ClassAv3 > 3e. The ClassAv2 is becomedFormeward ClassAv3 > > 4. All the instances of ClassAV3 have the correct format and everything > works. > > What is the problem: > =============== > > - When you do the first add instance variable, the old instances (the one > from ClassA) which are smaller (has 1 instance variable less) > have its class changed (after you perform a become of ClassA to ClassAv2). > So if you try to use them everything will explode, because you will trying > to access an instance variable that does not exists. > These instances are not referenced by anyone, however if you perform a > ClassAv2>>allInstances you will find them. So if you modify the class > adding two variables, one after another the second time > you will be accessing the invalid instances. > > > Considering the differences in the Become implementation > ============================================ > > However, the main difference is the implementation of the become forward. > Let's start with the new implementation, as it has not problems. > > When you do a become forward, from object a to b, the primitive replaces > the object a with a forwarder to b. > When this forwarded is accessed the references to it are rewrited. > If the objects are the same size (not this scenario) the object b replaces > object a. It does not produces an error because the old. > In the become forward the old instances are not keeped. > > In the old implementation the whole image is scanned, changing the > references to the old instances, replacing with references to the new > instances. > The old instances are not removed, just kept there to let the GC do its > work. > Again if the objects are the same size there is special behavior. > > I hope know the problem is better explained > > Cheers, > Pablo > > > > On Fri, Apr 14, 2017 at 10:50 AM, Igor Stasenko <siguctua(a)gmail.com> > wrote: > >> >> >> On 14 April 2017 at 10:19, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >>> But I do not get how doing that would handle the old instances? >>> Because you want to migrate the old instances. >>> >>> >> +1 >> there are no such thing as 'bad zombies', if they are there, it means you >> either don't care about migrating data >> or again, don't care about doing #becomeForward-ing them properly. >> In any case i don't see how GC could help to fix these issues. You either >> have consistency or don't have it, >> and GC cannot do anything magical to fix it. >> >> >> >>> Stef >>> >>> On Wed, Apr 12, 2017 at 1:26 PM, Denis Kudriashov <dionisiydk(a)gmail.com> >>> wrote: >>> >>>> >>>> 2017-04-12 13:17 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com> >>>> : >>>> >>>>> 1) each instance of A is becomed into its corresponding instance of >>>>> A' >>>>> 2) finally we become class A into A' >>>>> This step will make that old instances of A now have: >>>>> - the old format >>>>> - but point to the new class A >>>>> >>>> >>>> step 1) ensures that there are no instances of class A anymore. >>>> Check following script: >>>> >>>> c1 := Class1 new. >>>> c2 := Class2 new. >>>> c1 becomeForward: c2. >>>> Class1 allInstances "=> #()". >>>> >>>> >>>> And full migration is executed in high priority uninterrupted process >>>> to ensure that between 1) and 2) nobody will instantiate Class1 >>>> >>>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Pablo Tesone. > tesonep(a)gmail.com > -- Best regards, Igor Stasenko.

April 14, 2017

Re: [Pharo-users] Traits, method flatten

by Hilaire

Give a try to filein the correct .st source file of the Traits+Classes package. It does not get it right :( Pharo5 get it right when loading the .st source file though. Still investigating... Le 14/04/2017 Ã 11:04, Hilaire a Ã©crit : > - Test on Squeak, not sure how stable it is there... -- Dr. Geo http://drgeo.eu

April 14, 2017

Re: [Pharo-users] Export MongoDB to sql format

by Igor Stasenko

On 13 April 2017 at 22:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 13 Apr 2017, at 19:26, Asbath Sama biyalou via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > > > *From: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com> > *Subject: **Export MongoDB to sql format* > *Date: *13 April 2017 at 19:26:25 GMT+2 > *To: *Pharo users users <pharo-users(a)lists.pharo.org> > > > Hello Everyone. > > I think this is not the right place for this question. But I am doing a > work with Pharo. > > I use MongoDB with Voyage. But I am asked to export my database in sql > format. > > I want to know if there is a way to export mongoDB in sql. > > > there is not. > a nosql database will have problems to export its data as sql. > of course it can be done (as everything), but it is a manual task :S > > This sort of questions most strangest ones , that i always wonder.. Like people who buying microwave asking: cool , now how i could fit a coal burner to it? Why???? I mean if you need your traditional oven, they why even bother to buy a microvawe in a first place? cheers, > Esteban > > > Thanks. > > > Asbath > > -- Best regards, Igor Stasenko.

April 14, 2017