On 05-09-15 15:50, stepharo wrote:
Le 5/9/15 14:10, Stephan Eggermont a écrit :
On 05-09-15 08:52, stepharo wrote:
Are the fixes of yuriy addressing the nautilus one?
And there is a more difficult case where changing code in the debugger
does not get to (all) nautilus browsers. I had two browsers open and
changed code that was in the selected class but not visible in the
browsers. One browser was correctly updated, the other was not.
This has happened for a few weeks now, and I thought this was known
and related to the current Nautilus refactorings.
No Pharo is a complex system and we do not have enough tests.
Issue 16508 Nautilus loses track of changes when using the debugger
(restart)
50310 Linux
Open a nautilus browser
Add a new package Added
Add a new class SomeCase
Add a new method
SomeCase>>one
^1+self two
Save
Enter author name
Click on --all-- to get the method to show up (different bug)
Open a Playground
DoIt SomeCase new one
Create method two in debugger
SomeCase>>two
^2 + self three
Save
Restart (cursor is not correctly updated)
Proceed
Create a method three in debugger
SomeCase>>three
^3
Save
Proceed
Now, method three in the nautilus window is
SomeCase>>three
self shouldBeImplemented.
Open a new nautilus browser and verify that it has the correct method three
SomeCase>>three
^3
