- Pharo-users - lists.pharo.org

[ANN] MessageFlowBrowser updated for Pharo 5 + new video

by Torsten Bergmann

MessageFlowBrowser was updated for Pharo 5 (no deprecation warnings anymore). Also enjoy the new video: http://youtu.be/DRd_bzGocQg Have fun T.

April 6, 2016

Re: [Pharo-users] Debugger in 4.0

by Nicolai Hess

2016-04-05 20:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-04-05 20:37 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > >> See in the screenshot, >> >> contractRate is an instance variable. When evaluating it from the method >> variable pane, it seems to return an index. >> > > Ok, thats funny. > > >> >> When evaluating a method variable from the instance variable pane you >> get an undefined variable error... >> >> It used to be different before, and it is to say the least not >> convenient to debug >> > > I do not remember that I ever tried to evaluate a > method var / instance var > in the > instance / method > inspector pane. > > I now see the problem. For the context inspector, the compiler can generate code for evaluating the "printit on a variable" but for variables that are in fact instance variables, it does not generate an error because it resolves the variable name and index from the (object) instance scope. This is wrong I think. With that index, the code will access not the method object instance, but the context. It therefore reads some context instance data (stackpointer for exampe!). Are you sure this ever worked? I am afraid we can not fix this. Pharo 5.0 is about to release and it contains a new Debugger. The (old) spec debugger is still there, but it does not provide the printIt/doIt commands on the isntance and context inspector panes... > > >> >> >> Hilaire >> -- >> Dr. Geo >> http://drgeo.eu >> > >

April 6, 2016

Re: [Pharo-users] Updated Pharo by Example: First Example has problems

by Sean P. DeNigris

I don't think Doug is subscribed to the list. This message never made it past the Nabble mirror... dougt wrote > The Lights Out example will not close. The morphic halo will not appear > on the lights out grid. You have to close it with a statement in the > Playground. Judging from this forum, this problem is not new. I am > running Ubuntu 15.10 and a very recent version of Pharo 4.0 latest. > > Pharo has good documentation and is making an effort at keeping it > current. However, if the first example in the documentation has problems, > the potential Pharo user will conclude that there is not enough attention > to detail in the product, and move on to find a more solid product. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Updated-Pharo-by-Example-First-Example-has-problems-t… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

April 5, 2016

Re: [Pharo-users] Debugger in 4.0

by Nicolai Hess

2016-04-05 20:37 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > See in the screenshot, > > contractRate is an instance variable. When evaluating it from the method > variable pane, it seems to return an index. > Ok, thats funny. > > When evaluating a method variable from the instance variable pane you > get an undefined variable error... > > It used to be different before, and it is to say the least not > convenient to debug > I do not remember that I ever tried to evaluate a method var / instance var in the instance / method inspector pane. > > > Hilaire > -- > Dr. Geo > http://drgeo.eu >

April 5, 2016

Re: [Pharo-users] Debugger in 4.0

by Hilaire

See in the screenshot, contractRate is an instance variable. When evaluating it from the method variable pane, it seems to return an index. When evaluating a method variable from the instance variable pane you get an undefined variable error... It used to be different before, and it is to say the least not convenient to debug Hilaire -- Dr. Geo http://drgeo.eu

April 5, 2016

Re: [Pharo-users] Debugger in 4.0

by Hilaire

In the debugger, I want to write test code using both instance and method variables. As far as I can try it is not possible, or I missed something? Hilaire Le 05/04/2016 20:23, Nicolai Hess a Ã©crit : > I don't understand, in Pharo 4.0 the debugger bottom left pane contains the > instance variables and the right pane contains the method variables. > What is missing? > -- Dr. Geo http://drgeo.eu

April 5, 2016

Re: [Pharo-users] Debugger in 4.0

by Nicolai Hess

2016-04-05 16:43 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > From the debugger, in the bottom panes, when debugging in a bloc of > code, it seems impossible to access *at the same time* the instance > variables and the method variables. > > Am I missing something? > I don't understand, in Pharo 4.0 the debugger bottom left pane contains the instance variables and the right pane contains the method variables. What is missing? > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

April 5, 2016

Debugger in 4.0

by Hilaire

Hello, >From the debugger, in the bottom panes, when debugging in a bloc of code, it seems impossible to access *at the same time* the instance variables and the method variables. Am I missing something? Hilaire -- Dr. Geo http://drgeo.eu

April 5, 2016

Re: [Pharo-users] Slack invitation

by Esteban A. Maringolo

Welcome aboard! We're more than 150 members today. :) Esteban A. Maringolo 2016-04-05 6:40 GMT-03:00 Damien Cassou <damien.cassou(a)inria.fr>: > Damien Cassou <damien.cassou(a)inria.fr> writes: > >> can someone please invite me to pharoproject on slack? > > I got one. There was a dedicated section in http://pharo.org/community. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >

April 5, 2016

Re: [Pharo-users] [Pharo-dev] STON materialization corrupts a dictionary if the keys are references

by Peter UhnÃ¡k

> > Like I said, it is a hashing issue, sometimes it will be correct by > accident. > > I hope you did not have to much trouble with this bug, I guess it must > have been hard to chase. > The hardest thing often is to suspect the system or external libraries, but it wasn't that bad. Is it urgent ? > I can rehash it for now (I have a trivial case), but it should be fixed eventually (it wouldn't be so easy to rehash more complex structures). Thanks, Peter

April 5, 2016