I know this path of understanding code while it is running (inspector or debugger), but it is still a tedious path, and I feel Pharo is a bit under featured on that specific department, therefore my question on Moose.
Hilaire Le 09/01/2017 à 15:09, Tudor Girba a écrit : > That is why my advice is to not try too long to understand Pharo code > statically because this is not where the power of Pharo is. You are in a much > better position to understand a system when it’s running. So, the tools that > I use the most are the inspector when I need to understand structural > relationships or contracts between objects, and the debugger when I need to > understand some algorithmic steps. Even when I look for code structure > patterns, I mostly use the inspector because it allows me to query. Then you > augment these tools with custom views and you get quite far. -- Dr. Geo http://drgeo.eu
