March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3843 in pharo: isHealthy for HasedCollection

by pharo＠googlecode.com

Comment #4 on issue 3843 by ryd...(a)gmail.com: isHealthy for HasedCollection http://code.google.com/p/pharo/issues/detail?id=3843 Looks to me like something which belongs in the Testing trait for UnorderedCollections rather than in the UnorderedCollections themselves. (Collection testa were rewritten to use traits right, I'm not remembering incorrectly?)

March 22, 2011

[Pharo-project] [COTDC] 34#2 - MCStWriter

by laurent laffont

Today: MCStWriter Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

March 22, 2011

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously

by laurent laffont

On Tue, Mar 22, 2011 at 1:23 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > continue > please continue > > OK I will change the process a little. One COTDC per day. If no or not satisfying comment I will not put it in results. So I abort this one. Laurent. > > Stef > On Mar 22, 2011, at 8:14 AM, laurent laffont wrote: > > > Hi people, > > > > almost no participation in COTDC last days. > > > > I'm not a Smalltalk guru and even 30mn to look at code is sometimes not > enough for me to understand some stuff alone. > > > > I like COTDC because of > http://code.google.com/p/pharo/wiki/CommentOfTheDayContest ==> > documentation. > > > > But quality / good comment is needed and there's ~600 classes without > comment remaining. So if we want a 100% good commented Pharo in 2 years from > now, we should do it every day. > > > > Laurent Laffont > > > > On Mon, Mar 21, 2011 at 8:36 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Could it be: > > > > I parse PackageInfo statement from Monticello packages file. > > > > Laurent. > > > > > > > > On Mon, Mar 21, 2011 at 8:02 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > > Today: MCSystemCategoryParser > > > > > > Comment Of The Day Contest - One Day One Comment > > Rules: > > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > > #2: If you cannot comment it, deprecate it. > > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > > > Laurent > > > > > > >

March 22, 2011

Re: [Pharo-project] Issue 2672 in pharo: Remove UpdatingXXXMorph ....

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #3 on issue 2672 by marcus.d...(a)gmail.com: Remove UpdatingXXXMorph .... http://code.google.com/p/pharo/issues/detail?id=2672 (No comment was entered for this change.)

March 22, 2011

Re: [Pharo-project] Issue 2543 in pharo: RealEstateAgent should be cleaned

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #2 on issue 2543 by marcus.d...(a)gmail.com: RealEstateAgent should be cleaned http://code.google.com/p/pharo/issues/detail?id=2543 (No comment was entered for this change.)

March 22, 2011

Re: [Pharo-project] Issue 3840 in pharo: ivar errorHandler in Process seems to be unused

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3840 by marcus.d...(a)gmail.com: ivar errorHandler in Process seems to be unused http://code.google.com/p/pharo/issues/detail?id=3840 in 13103

March 22, 2011

[Pharo-project] [update 1.3] #13103

by Marcus Denker

13103 ----- Issue 3821: makeStrong/makeWeak contains a bug Issue 3843: isHealthy for HasedCollection Issue 3840: ivar errorHandler in Process seems to be unused -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 22, 2011

Re: [Pharo-project] Issue 3843 in pharo: isHealthy for HasedCollection

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3843 by marcus.d...(a)gmail.com: isHealthy for HasedCollection http://code.google.com/p/pharo/issues/detail?id=3843 I think I clicked on the delete button by accicdent instead of "View". In 13103.

March 22, 2011

Re: [Pharo-project] test crashing the cog vm

by Alexandre Bergel

Ok Alexandre On 22 Mar 2011, at 11:40, Toon Verwaest wrote: > Grmbl. Seems broken indeed. I reinstalled it. Still some work to be done on coloring :) > > If you are interesting in the translation part from Smalltalk to Schemetalk, it can be found at: > https://www.iam.unibe.ch/scg/svn_repos/Sources/SchemeTalk/smalltalk > > The parser is basically a petit-parser like PEG parser written in Schemetalk. The translator compiles the pharo filed-out sources to schemetalk code and/or loads the generated code. Then there's some stuff that avoids "bad" definitions that only serve to make pharo run fast on the pharo VM, such as "fixtemps" and whileFalse:, whileTrue: which don't convey their proper semantics but rather just recursively end up in the same method hoping that the bytecode evaluation will do the proper thing. > > Unfortunately I didn't write about the squeak->schemetalk conversion; since I just considered it a silly exercise ... I guess I could if someone's interested. > > cheers, > Toon > > On 03/22/2011 05:23 PM, Alexandre Bergel wrote: >> I tried to have a look at SchemeTalk. Apparently the website is not up to date. I reached http://www.iam.unibe.ch/~verwaest/blog/?p=6 from http://scg.unibe.ch/research/schemetalk >> >> Alexandre >> >> >> On 22 Mar 2011, at 11:16, Toon Verwaest wrote: >> >>> On 03/22/2011 05:10 PM, Alexandre Bergel wrote: >>>> I see your point and I suspected you spoke according to your experience. I am just trying to make people innovate, in my own way. >>>> >>>> Another thing. Keeping the VM small will definitely help when moving to a different executing platform. It would be amazing to have the Pharo running on Javascript VM. >>> That's not even that hard. I even had Pharo running on top of my own SchemeTalk already, after 2 days of hacking. I only stopped where I bumped into traits, since I didn't find any bootstrapping script for traits. >>> >>> I would basically compile all the smalltalk code to equivalent schemetalk code (very easy since the models are very similar), and compile all the natives to function-calls that perform what the native should perform. These functions had names that wouldn't clash with the Smalltalk names so you couldn't refer to it directly. >>> >>> Obviously in the end you would have all the smalltalk code running with SchemeTalk syntax, but all the code was virgin Pharo code. Very fun stuff :) >>> And if you do it this way, it doesn't really depend on your VM anyway, since I was executing Smalltalk code as Scheme code, not as Smalltalk bytecodes interpreted by schemecode. That's a lot faster. >>> >>> cheers, >>> Toon >>>> Alexandre >>>> >>>> >>>>> Ok, I very much understand this point of view. That's exactly why I started Pinocchio. >>>>> >>>>> I'm currently building my 4rd iteration. I started building a Smalltalk by having AST evaluation (actually I started out with self-evaluating AST objects that got evaluated by sending message... :D) . Then moved on to stack-based bytecodes. Then moved on to registered-based bytecodes (where I am now). All of my progress has been made by careful scrutinizing of the problems at hand. I did reevaluate and question all steps; and I'm a bit sad that I ended up doing it this way... But then I guess there is some inevitability in it. >>>>> >>>>> For example the register-based bytecodes, I had no idea that what I was doing were register-based bytecodes until I read the Lua VM description and noticed that it was exactly the same. >>>>> >>>>> However I do think that I learned a lot by doing it. I made the trade-offs myself and understand them a lot better than I did before. What I'm defending in this discussion isn't based on estimates but experience from building it from the ground up. >>>>> >>>>> And this is where I welcome everyone to do the same! It took me 2 years to get to where I am now, but maybe it goes faster for you ;) It is definitely a very worthwhile exercise. And I think because of it I'm finally at the point where I can contribute something... >>>>> >>>>> cheers, >>>>> Toon >>>>> >>> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 22, 2011

Re: [Pharo-project] Issue 3821 in pharo: makeStrong/makeWeak contains a bug

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3821 by marcus.d...(a)gmail.com: makeStrong/makeWeak contains a bug http://code.google.com/p/pharo/issues/detail?id=3821 in 13103

March 22, 2011